Return-Path: Delivered-To: apmail-jakarta-tomcat-user-archive@apache.org Received: (qmail 15845 invoked from network); 4 Feb 2003 23:43:37 -0000 Received: from exchange.sun.com (192.18.33.10) by daedalus.apache.org with SMTP; 4 Feb 2003 23:43:37 -0000 Received: (qmail 20544 invoked by uid 97); 4 Feb 2003 23:45:11 -0000 Delivered-To: qmlist-jakarta-archive-tomcat-user@nagoya.betaversion.org Received: (qmail 20537 invoked from network); 4 Feb 2003 23:45:10 -0000 Received: from daedalus.apache.org (HELO apache.org) (208.185.179.12) by nagoya.betaversion.org with SMTP; 4 Feb 2003 23:45:10 -0000 Received: (qmail 14406 invoked by uid 500); 4 Feb 2003 23:43:18 -0000 Mailing-List: contact tomcat-user-help@jakarta.apache.org; run by ezmlm Precedence: bulk List-Unsubscribe: List-Subscribe: List-Help: List-Post: List-Id: "Tomcat Users List" Reply-To: "Tomcat Users List" Delivered-To: mailing list tomcat-user@jakarta.apache.org Received: (qmail 14394 invoked from network); 4 Feb 2003 23:43:18 -0000 Received: from unknown (HELO newkenny.msoft.com) (63.143.111.130) by daedalus.apache.org with SMTP; 4 Feb 2003 23:43:18 -0000 Received: from Will ([192.168.2.165]) by newkenny.msoft.com with Microsoft SMTPSVC(5.0.2195.5329); Tue, 4 Feb 2003 15:41:49 -0800 Message-ID: <05b901c2cca7$a86d3810$01000001@Will> From: "Will Hartung" To: "Tomcat Users List" References: Subject: Re: Sessions across browser restarts Date: Tue, 4 Feb 2003 15:46:37 -0800 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.50.4807.1700 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4807.1700 X-OriginalArrivalTime: 04 Feb 2003 23:41:49.0703 (UTC) FILETIME=[FCC26170:01C2CCA6] X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N > From: "Zabel, Ian" > Sent: Tuesday, February 04, 2003 2:35 PM > Subject: RE: Sessions across browser restarts > I believe that just controls the timeout of the session on the server, and > maybe the timeout of the cookies. To be more specific, I am asking about the > timeout of the jsessionid cookie on the client. Is it possible to control > these separately, i.e., set session-timeout to 30 minutes, but make the > jsessionid cookie expire when the browser is closed, or alternatively, make > the cookie expire in 30 minutes, so the user could close his browser, and > come back to the app later and still maintain his session. Yeah, you'll need to go into the core Session processing code I think to alter the attributes of the session tracking cookie, being as it's essentially opaque to the application (i.e. you know sessions exist, but you should not rely on the actual mechanism of how they are implemented). What this also means is that if you tweak the actual Session code within Tomcat, then your application will lose portability across containers. To pull it off, you might want to look at subclassing the stock Tomcat SessionManager (I think) class and using your version in the server.xml file. However, if you want this kind of functionality, and you want it portable, you'll need to write your own session management code for the attributes that you wish to persists past a browser closing. Of course, depending on the state your managing, this doesn't have to be an onnerous task. But it is a bit of a pain in the neck in a "reinventing the wheel" kind of way. Regards, Will Hartung (willh@msoft.com) --------------------------------------------------------------------- To unsubscribe, e-mail: tomcat-user-unsubscribe@jakarta.apache.org For additional commands, e-mail: tomcat-user-help@jakarta.apache.org