Hi Joel,
If you're using custom (modeled) authentication (or no authentication at all), you can store the original session-id/user-id in the client, and add a timer that checks the logged-in user (or session id) against the original. If the logged-in user is null (or if session id has changed) a timeout has occurred.
Regards,
David
To use the full functionality of this web site, JavaScript needs to be turned on.
For best results, use the Firefox browser..
Copyright © 2003-2017 - Tersus Software Ltd., All rights reserved. Terms of Use License Graphic design by EmaraDesign