Tech blogg

There are several issues you should be aware of when implementing this solution. First of all, session timeouts exist to prevent excessive memory being held up on the server. You may say that I can just increase the SessionTimeout parameter in web.config to let˙s say 2 hours, and problem solved! However, imagine a timeout value of 2 hours on a high traffic site, holding all session data for thousands of user sessions. There is also another problem - and usually related to the previous issue. In the case of shared hosting, you may not even have access to the session timeout, simply because the memory usage has to be controlled. On such systems, web applications often tend to timeout after only 15 minutes, regardless of your settings in the web.config file.

Well, here is a solution that will solve these issues, and avoid session timeouts. Use this solution with caution, as there could be security risks involved in not having web applications time out. The proposed solution relies on javascript, jQuery and a server program (a HttpHandler - SessionRefresh.ashx). The javascript I use is the setInterval function which will run a javascript function at set intervals. This means that we can call the jQuery $.post method at predefined intervals, which will then post to the server, and as a result keep the session alive.

Here is the HttpHandler - SessionRefresh.ashx


<%@ WebHandler Language="C#" Class="SessionRefresh" %>

using System;
using System.Web;
using System.Web.SessionState;

public class SessionRefresh : IHttpHandler, IRequiresSessionState
{
    public void ProcessRequest(HttpContext context)
    {
        context.Session["SessionRefresh"] = DateTime.Now;
    }

    public bool IsReusable
    {
        get
        {            return false;        }
    }
}

All this routine is doing is to update a session object with the current date and time, and thus effectively keeping the session alive. How do we call this program then. Well this is where the javascript and jQuery comes into the picture. Here is the code you should have on your client.

<script type="text/javascript">

$(function () {

    setInterval(SessionRefresh, 540000);  //((10min * 60sec/min) - 60sec) * 1000msec/sec = 540.000msec    Set 10min SessionTimeout in web.config.

});

function SessionRefresh() {

    $.post("/SessionRefresh.ashx", null, function () {

        $("#testResult").append("<p>Session updated!<p/>");

    });

}

</script>

 Your code goes here....

<div id="testResult"></div>

The last <div...> is of course there for testing purposes. When the program "SessionRefresh.ashx" executes, the text "Session updated!" is written back into the "div" element.


Happy refreshing :)

André Vold