04-24-2019, 05:51 AM
Yes, as Pete says, SessionTimeout with keepalive is mainly for detecting when the browser disappears. It sometimes makes sense to time your user's activity in some other way. I have done that.
Also, as Chad has indicated, SessionTimeout doesn't care whether a user or some other activity tickles it. It starts over when the browser does something to indicate it's still there. KeepAlive works exactly that way, as Pete described, it just sends a simple message to tickle the server.
If you take an empty form with a SessionTimeout and no Keepalive, your session WILL time out. Add simple controls and it will still timeout. Add some automatic refresh or other trigger and it won't.
You might want to play with it some. That's the best way to find the boundaries and behavior.
Dan
Also, as Chad has indicated, SessionTimeout doesn't care whether a user or some other activity tickles it. It starts over when the browser does something to indicate it's still there. KeepAlive works exactly that way, as Pete described, it just sends a simple message to tickle the server.
If you take an empty form with a SessionTimeout and no Keepalive, your session WILL time out. Add simple controls and it will still timeout. Add some automatic refresh or other trigger and it won't.
You might want to play with it some. That's the best way to find the boundaries and behavior.
Dan