Headless client is basically JSP using "servoy aware" beans, so I guess that the timeout for a client session is the default used by Tomcat, which is 30 minutes.
You could lower that timeout by altering your web.xml file located in /Servoy/application_server/server/webapps/ROOT/WEB-INF/
with something like (unit is minutes):
- Code: Select all
<session-config>
<session-timeout>10</session-timeout>
</session-config>
before the ending </web-app> tag.
So in the example above, I have shortened the session to 10 minutes.
Be aware though, that by doing so you are shortening the life span of a session, meaning that if a user leave its browser open and go grab a coffee and start chatting with a colleague... if there is no browser activity for +10 minutes, his session will be lost (meaning that he will probably need to authenticate again, and if he was on a form and had began some editing, all his changes will be lost).
There are workaround for this, like using Ajax to periodically "ping" the server if the browser is still open, or having an invisible frame with a meta-refresh or a javascript which updates the page every 9,5 minutes.
I do it like that on all my web developments and I have people connected for hours on my system from the early morning to the evening with an hour lunch inactivity, if they leave their browser open, they keep their session open, if they don't then the session is closed after only 10 minutes (which is quite low in web standards).
Hope this helps,