SessionExpired is sent to any scripts that have been deemed inactive.
SessionExpired is sent to a script if the following criteria is satisfied:
GotRequestevents for an amount of time equal to or greater than the cleanup period of the HTTP provider, which is by default
SessionExpiredevent. The HTTP Provider uses the occurrence of a no handler to indicate that the script is no longer running, or that it does not define an event handler for
SessionExpired. In either case, this means to the HTTP provider that the script instance does not need to be informed of a session expired event and that it will no longer attempt to send the
SessionExpiredevent to that script instance.
Upon receiving the
SessionExpired event, what should be done is entirely up to the developer; the application server places no expectations or requirements on the script instance. Specifically, it is not required that the script instance come to an end when
SessionExpired occurs; however, it is reasonable to expect that a large percentage of scripts will indeed end with the occurrence of this event, since it indicates inactivity of over 20 minutes. Couple this amount of inactivity with the session-less nature of HTTP and the inherent difficulty of tracking the state of the user of the application, one can see why most scripts would end when this event occurs. If the developer chooses to not end the script upon receiving the
SessionExpired event, then
SessionExpired events will continue to fire for that script until one of the conditions is met in the above list.
If you end a script at any point, one can use the
SessionEnd action to indicate to the HTTP Provider that it can release the session from it's memory. In other words, it no longer will track this script instance any longer.
No Event Parameters