Return-Path: Delivered-To: apmail-tomcat-users-archive@www.apache.org Received: (qmail 61438 invoked from network); 17 Sep 2009 08:57:26 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 17 Sep 2009 08:57:26 -0000 Received: (qmail 38423 invoked by uid 500); 17 Sep 2009 08:57:21 -0000 Delivered-To: apmail-tomcat-users-archive@tomcat.apache.org Received: (qmail 38359 invoked by uid 500); 17 Sep 2009 08:57:21 -0000 Mailing-List: contact users-help@tomcat.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: "Tomcat Users List" Delivered-To: mailing list users@tomcat.apache.org Received: (qmail 38348 invoked by uid 99); 17 Sep 2009 08:57:21 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 17 Sep 2009 08:57:21 +0000 X-ASF-Spam-Status: No, hits=1.2 required=10.0 tests=SPF_NEUTRAL X-Spam-Check-By: apache.org Received-SPF: neutral (nike.apache.org: local policy) Received: from [193.252.22.128] (HELO smtp5.freeserve.com) (193.252.22.128) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 17 Sep 2009 08:57:11 +0000 Received: from me-wanadoo.net (localhost [127.0.0.1]) by mwinf3407.me.freeserve.com (SMTP Server) with ESMTP id BEBAC1C00083 for ; Thu, 17 Sep 2009 10:56:50 +0200 (CEST) Received: from me-wanadoo.net (localhost [127.0.0.1]) by mwinf3407.me.freeserve.com (SMTP Server) with ESMTP id B17831C00085 for ; Thu, 17 Sep 2009 10:56:50 +0200 (CEST) Received: from mx01.dev.local (unknown [91.109.150.55]) by mwinf3407.me.freeserve.com (SMTP Server) with ESMTP id 873011C00083 for ; Thu, 17 Sep 2009 10:56:50 +0200 (CEST) X-ME-UUID: 20090917085650553.873011C00083@mwinf3407.me.freeserve.com Received: from localhost (localhost [127.0.0.1]) by mx01.dev.local (Postfix) with ESMTP id B880032174 for ; Thu, 17 Sep 2009 09:56:44 +0100 (BST) X-Virus-Scanned: Debian amavisd-new at homeinbox.net Received: from mx01.dev.local ([127.0.0.1]) by localhost (mx01.dev.local [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id NcN6v6HSs-jU for ; Thu, 17 Sep 2009 09:56:39 +0100 (BST) Received: from [192.168.0.9] (study03.dev.local [192.168.0.9]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx01.dev.local (Postfix) with ESMTPSA id 126E73215C for ; Thu, 17 Sep 2009 09:56:39 +0100 (BST) Message-ID: <4AB1F9B5.1030800@apache.org> Date: Thu, 17 Sep 2009 09:56:21 +0100 From: Mark Thomas User-Agent: Thunderbird 2.0.0.23 (Windows/20090812) MIME-Version: 1.0 To: Tomcat Users List Subject: Re: Tomcat Realm Auto-Relogin after Session-Timeout Problem References: <4AB149F8.7020005@christopherschultz.net> <25487080.post@talk.nabble.com> In-Reply-To: <25487080.post@talk.nabble.com> X-Enigmail-Version: 0.96.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org atroiano wrote: > > Christopher Schultz-2 wrote: >> >> This is a question that you will have to answer: what information is >> absolutely necessary for you to resume a user interaction in-progress? >> Whatever that is, you'll need to include that information in every >> single link that a user can click on (or in every form they can submit). >> > > > The problem is that to resume a user interaction in-progress after a > re-login > I need informations binded as attributes in the expired session. > After a re-login I would like to 'resume' old session instead of to use e > new empty one. > > Is it possible? The way you describe? No. If you want this then you have a couple of options: a) Do what Chris said and pass state back and forth in the request/repsonse b) Buy more memory and have longer session expiration times c) Look into using the persistent session manager Mark --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org For additional commands, e-mail: users-help@tomcat.apache.org