Hallo Bruce,
>>If you use the count-down timer then a URL is triggered when the count-down expires. But that call can have the effect of "touching" the session, and hence extending it for a further period. So the user is told "The session has ended" but in fact the session may actually exist for another cycle (typically 15 minutes.)
This is correct I tested before and I knew after the session expire will open the login form and it will extend again the session with another xx minutes you have setup in template.
For my project it was necessary to know when this session expire because I develop a mechanism to show user online and how much time they spend in one session. My code for logout is on Webhandler > DeleteSession. This works perfect. But when session expire then I have to wait again xx minutes until this embed execute the code so this will not reflect correct time spend for a user in that session.
Now I made a trick. I put a parameter on the link "?sessionexpire=1"
p_web.Script('startCountDown('& int(p_web.site.SessionExpiryAfterHS/100) &',"'& clip(p_web.site.LoginPage) &'?sessionexpire=1'&'","countdown");')
and I read this parameter on the login page. If true then my code execute. For the moment it works ok.
If anyone have better method please share
)
Thank you,
Robert