session-state

I set a session object at one juncture in my code: Session("my_name") = "Dave" Later in my code I give the user a chance to update this object: Session("my_name") = TextBox1.Text I reload my page and display a little hello statement like this: Label1.Text = "Hello" & CStr(Session("my_name")) The result is: "Hello Dave" no matter what I change Session("my_name") too. EDIT: Here is the a full code-behind I wrote up to demonstrated: Public Class WebForm1 Inherits System.Web.UI.Page Protected Sub Page_Load(ByVal sender As Object, ByVal e As System.EventArgs) Handles Me.Load Response.Cache

I have a web service built for SharePoint 2007 that I am trying to port to SharePoint 2010. This web service is dependent on session state to function properly, but so far, I have been enable to get session state to work at all in SharePoint 2010. This web service runs as its own web application under t he /_vti_bin virtual directory. I have tried all of the following with no luck: Ensured the "State Service" service application is running. Added the System.Web.SessionState.SessionStateModule http module to my application's web.config file. Added the System.Web.SessionState.SessionStateModule

What is the difference between Session.Abandon() and Session.Clear() in ASP.Net? Session.Abandon() will end the current session. Session_End will be fired and the next request will fire the Session_Start event. Session.Clear will just clear the session data and the the session will remain alive. Session ID will remain the same in both cases, as long as the browser is not closed. In a nutshell: Session.Abandon(); cancels the current Session . Session.Clear(); clears all values from Session state. Session.Abandon() will destroy/kill the entire session. Session.Clear() removes/clears the session

I often hear people saying that session scoped objects should implement Serializable ? Why it is so ? What will be the result if one doesn't do this ? Why not make this a part of the servlet specification then ? I know Tomcat doesn't complain if we do not do this . What about other app servers like JBoss, WebSphere or Weblogic ? This allows the servlet container to either store the contents of a session on disk, or to transfer session contents over the network to another server. Why does the container need to store session on the disk (passivation)? Perhaps when the memory is full. When the

I have following configuration in web.xml in tomcat 7. I am wondering if I can add any configurable parameter here, so that if user tries to do any operation post 30 minutes, I redirect the user to our home page. <session-config> <session-timeout>30</session-timeout> <cookie-config> <domain>mydomain.mycompany.com</domain> <http-only>true</http-only> <secure>false</secure> </cookie-config> <tracking-mode>COOKIE</tracking-mode> </session-config> ohwhy This is probably not possible by configuration only. You will have to add a filter aswell. One way of doing that is described here: https:/

The stateless web application seems promising . How to make one? Especially with Spring WebMvc? Any guidelines? Here are a few things on my mind: Avoid creating session Use a centralized storage for state info and share that among web application instances. ADD 1 I think it is not a question of whether to keep state info or not. State info is always necessary if you want to do something useful. It is actually a question where/how to keep the state info. This article is useful. It mentioned in-proc/out-of-proc session, data cache, and why not to use session. Related: Use Spring MVC for

We've migrated our webapplication from .net runtime 2 (v 3.5) to .net runtime 4 (v 4.5) and I have a question for deployment. Our sessionstate server is a "stateserver", and runs aspnetsession from framework 2 on a separate server. When we deploy and upgrade the application pool to .net 4 to one of our webservers in test, it seems that the session expires or is dropped somehow as we're redirected to the logon page of our application. Is there any way of deploying our new version of the app without our users losing session in the process? Are the sessioncookie created by application pools