SignalR connections (including the connection underlying all Hub operations for a client) do not support Session state. You could enable it if you wanted to but we’d strongly recommend against it as session state access serializes requests for a given client, meaning you won’t really get the benefit from SignalR duplex messaging anymore, as one … Read more
Session is used for the TempData store. TempData is a highly limited form of session state which will last only until the next request from a certain user. (Edit In MVC 2+, it lasts until it is next read.) The purpose of TempData is to store data, then do a redirect, and have the stored … Read more
As you mentioned, common ways to implement HTTP session tracking include URL rewriting and cookies. Session tracking basically requires that a session ID is maintained across multiple requests to the server. This means that each time a given client makes a request to the server, it passes the same session ID. The server can use … Read more
One of the fundamental principles of frameworks like ASP.NET MVC is that they are stateless, just like the Web is. ASP.NET Web Forms is an attempt to mimic a stateful paradigm over a stateless enviroment. It is a lie, in other words. Using Session variable in an ASP.NET MVC application is a bit like tying … Read more
There are 2 REST answers to this, depending on what specifically you are trying to do. If you are truly trying to manage request-based state (such as when a user is working through a multi-screen wizard or some other navigation-based workflow), then the REST answer is that state should be sent back-and-forth with each request/response … Read more
I came up with a pretty awesome solution to this. What I’ve implemented was when user “Bob” logs in from their PC, and then the same user “Bob” logs in from another location, the log-in from the first location (their PC) will be killed while allowing the second log-in to live. Once a user logs … Read more
They are absolutely the same. RemoveAll calls Clear internally. From Reflector: public sealed class HttpSessionState : ICollection, IEnumerable { … [TargetedPatchingOptOut(“Performance critical to inline this type of method across NGen image boundaries”)] public void RemoveAll() { this.Clear(); } … }
First of all I say that MS asp.net have lock in the core of “asp.net processing a page” the session, somewhere in the “webengine4.dll” dll for asp.net 4 And I say that from the view point of MS asp.net act correct and lock the session this way because asp.net can not know what type of … Read more
Implement the System.Web.SessionState.IRequiresSessionState interface public class Handler : IHttpHandler, System.Web.SessionState.IRequiresSessionState { public void ProcessRequest(HttpContext context) { context.Session[“StackOverflow”] = “overflowing”; context.Response.Redirect(“~/AnotherPage.aspx”); } }