I seem to be getting different answers on this subject, but I am trying to implement a session countdown timer on my main page which
utilizes a web tab. The core of my application is hosted on three different tabs but the countdown timer is stored in my header which sits
just above the web tab definition.
So question: when switching between tabs (with all tabs loaded by contenturl definitions), does the session get extended during AJAX
postbacks? When a button is clicked to perform an action, the Page_Load method fires and one of the first things you do is to check
the Postback variable as you do certain functions if you are in a "Postback" situation or not. So, if "!Postback" condition is the case,
does a Session get extended?
I can understand if this topic is somewhat unrelated to webtabs themselves, but given that my countdown timer sits parallel to the webtab,
I find it relevant. I do have the jscript in place and the countdown does get launched and it the timer updates, but don't know when
the session gets extended.
Paul
Hello Paul,
I'm glad that you were able to resolve your issue.
Best regards,Martin PavlovInfragistics, Inc.
I figured out what I need to do to extend the session whenever an action takes place (whenever a tab is changed or when a button is pressed). I invoke an AJAX request to a handler that requires session state. This alone resets the timeout. So, session is extended in the backend without requiring a full page reset.
Please, excuse me, but I don't think I understand your question. Can you, please explain with a little more detail.
Thanks in advance,Martin PavlovInfragistics, Inc.
Fair enough. Aside from that, anything of the infragistics controls or asp.net controls that are loaded within an update panel do not necessary extend the session. However a reload of the tab (i.e., the control URL), will cause the session to be reset.
What are your WebTab's PostBackOptions? I guess that if you enabled "EnableReloadingOnTabClick" option the session should get extended.
Basically the WebTab doesn't contain any session related code, but if the pages configured in Tab's ContentUrl are reloaded each time a tab is activated then the session cookie is sent to the server as part of the request.