Re: Http Session timeout clock

There's session timeout and thread timeout on an individual request.

I'm guessing your scenario solves the web session timeout, but not an individual thread timeout or does it ? :-)

Regards,
Richard Schoen
RJS Software Systems Inc.
Where Information Meets Innovation
Document Management, Workflow, Report Delivery, Forms and Business Intelligence
Email: richard@xxxxxxxxxxxxxxx
Web Site: http://www.rjssoftware.com
Tel: (952) 736-5800
Fax: (952) 736-5801
Toll Free: (888) RJSSOFT
------------------------------

message: 6
date: Thu, 12 Apr 2012 16:39:05 +0000
from: Jorge Merino <jorge@xxxxxxxxx>
subject: Re: [WEB400] Http Session timeout clock

The solution that worked for me on a web page like the one that you mention, rather to mess up with the server, I included a 'keepalive' javascript call to the server during the web session.

Every 100 seconds for instance, your web page should connect to the URL to get a 1x1 pixel size image but changing the URL with the timestamp to avoid the browser to grab it from the cache: http://yourwebsite.com/imageonepixel.jpg?20120412103507

Look into this example for more details:
http://www.intelliproject.net/articles/showArticle/index/js_session_expired

Another example using Ajax:
http://blog.dayspring-tech.com/blog/2007/01/16/keep-session-alive-js-code/


jmerinoh