Peter, there seems to be something wrong with what you are saying there. Closing a browser can not trigger a session end event. It however will assign a new session id via CFID & CFToken.. but the actuall session variables still exist in the persistant scope until they expire by the server during the timeout.
This can be achieved, byt doing a simple test. If you know how to test it. On 5/14/07, Peter Tilbrook <[EMAIL PROTECTED]> wrote: > > > For me if the Session has been terminated (albeit an error or > something made programmatically) then handling of it is crucial. > Unfortunately for me my host does not use J2EE sessions - at all - and > that sucks. > > If the browser (client) is closed - session is terminated. This is > what happens if using J2EE sessions. If not - as my host does - then a > session can be restored by relaunching the browser and opening the > same session. Scary shit but that is what my host does. > > So I store nothing in a scope that can be abused - but the session > issue is bloody difficult to avoid. > > > > -- Senior Coldfusion Developer Aegeon Pty. Ltd. www.aegeon.com.au Phone: +613 8676 4223 Mobile: 0404 998 273 --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "cfaussie" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/cfaussie?hl=en -~----------~----~----~----~------~----~------~--~---
