Session Idle-Timeout instead of Cutoff

[nepdev]

In OVD version 3.0.3, if I configure any other session timeout than "none", it will warn me a few minutes before this times out and then close the session. This is independent whether I am actually actively working in OVD or not - it will always close it.

This means that if a user happens to be in the middle of some work just before the time out he will inevitably use that data if he is not right at his desk when the warning gets issued. And even if he is at his desk he has no way to interrupt or stop that shutdown. No matter what he does, he has no choice. That can create quite some upsets, as this behaviour isn't expected, at least not for Windows users.

It would be much more intuitive if the session timeout would work like a screen saver does - the timeout value is counted from a point of inactivity (no user action in the client), and the timeout value ticks forward from that. Any user interaction thereafter resets the timeout counter back to zero. 

As the client is Java based and is the only channel any user interaction goes through for this specific user, I would assume this type of setup should be relatively simple to implement. It would make quite some difference to user friendliness.