Details
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
Field | Original Value | New Value |
---|---|---|
Salesforce Case | [] | |
Fix Version/s | 2.0-Beta2 [ 10242 ] |
Repository | Revision | Date | User | Message |
ICEsoft Public SVN Repository | #22474 | Thu Sep 30 10:12:58 MDT 2010 | ted.goddard | strictSessionTimeout config ( |
Files Changed | ||||
![]() ![]() ![]() |
Assignee | Ted Goddard [ ted.goddard ] |
Status | Open [ 1 ] | Resolved [ 5 ] |
Resolution | Fixed [ 1 ] |
Salesforce Case | [] | |
Affects | [Documentation (User Guide, Ref. Guide, etc.)] |
Fix Version/s | 2.0.0 [ 10230 ] |
Status | Resolved [ 5 ] | Closed [ 6 ] |
Additional APIs should be added to allow the application to determine when the last user event and last push update has occurred.