Session Idle Timeout instead of Fixed Expiry Time

39 views
Skip to first unread message

nepdev

unread,
Oct 11, 2012, 4:51:12 PM10/11/12
to ulteo-ovd-comment...@googlegroups.com
It would be very natural to expect a session time-out work like this:

I set a certain time such as 30 minutes. If there is no activity from the user for this length of time at all, OVD will disconnect the session. This would mean if the user has not been typing on the keyboard or moving the mouse for longer than 30 minutes, the session disconnects. In effect this would also mean if the user is busily typing or moving the mouse all the time, there will never be any session exit.
An additional setting should then control if such a session is "timeout-persistent", i.e. if the user is having any applications which were open still being open or not.
(This would be similar to leaving an Ulteo session - if I leave it by closing the browser itself, it displays a message "Do you want to leave this page?" and it will actually keep the programs still running (or whatever it does to keep it persistent) - i.e. if I log back in I will have my apps open again as if I had not gone out (with "session persistent"= "yes"). If I close the session with the QUIT button at the right-hand bottom edge of the page, then it definitely closes everything, and I'll be greeted with an empty desktop if I log back in.)

In any case, the key point is that it is very unnatural for the server to just force an exit after x minutes even if I am busily typing a document. It is sort of rude to force me out of there.

Right now, I can avoid the forced exit only by setting time-out to "none".
But the problem is really that users ARE going to "forget" to close their sessions, so they ARE going to keep being open and use up server resources even if not used. So they should just be reclaimed by the server. But only if they are really not used by the user.

 
Reply all
Reply to author
Forward
0 new messages