Details
Improvement
Major
Description
In some cases, push activity alone should not be considered session activity, and the session timeout should occur if the user has not been active within the configured session timeout. To implement this, ICEfaces must inspect incoming requests and invoke
externalContext.invalidateSession();
when the session is deemed inactive. This can interfere with applications that contain a mixture of ICEfaces and non-ICEfaces pages and can result in dashboard-type applications being disconnected unexpectedly.
externalContext.invalidateSession();
when the session is deemed inactive. This can interfere with applications that contain a mixture of ICEfaces and non-ICEfaces pages and can result in dashboard-type applications being disconnected unexpectedly.
Activity
- All
- Comments
- History
- Activity
- Remote Attachments
- Subversion
It should also be configurable whether an active push connection is sufficient to keep the session alive (even if no page updates have occurred within the timeout interval).
Show
Ted Goddard
added a comment - It should also be configurable whether an active push connection is sufficient to keep the session alive (even if no page updates have occurred within the timeout interval).
Verified with auction. It may be desirable to add the strictSessionTimeout config to auctionMonitor.
Show
Ted Goddard
added a comment - Verified with auction. It may be desirable to add the strictSessionTimeout config to auctionMonitor.
Additional APIs should be added to allow the application to determine when the last user event and last push update has occurred.