Return-Path: Delivered-To: apmail-xml-cocoon-dev-archive@xml.apache.org Received: (qmail 37545 invoked by uid 500); 7 Apr 2003 22:09:24 -0000 Mailing-List: contact cocoon-dev-help@xml.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: list-post: Reply-To: cocoon-dev@xml.apache.org Delivered-To: mailing list cocoon-dev@xml.apache.org Received: (qmail 37524 invoked from network); 7 Apr 2003 22:09:23 -0000 Received: from unknown (HELO pulse.betaversion.org) (217.158.110.65) by daedalus.apache.org with SMTP; 7 Apr 2003 22:09:23 -0000 Received: (qmail 3949 invoked from network); 7 Apr 2003 22:09:28 -0000 Received: from unknown (HELO apache.org) (stefano@80.105.91.155) by pulse.betaversion.org with SMTP; 7 Apr 2003 22:09:28 -0000 Message-ID: <3E91F743.2030003@apache.org> Date: Tue, 08 Apr 2003 00:10:11 +0200 From: Stefano Mazzocchi User-Agent: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.3) Gecko/20030312 X-Accept-Language: en-us, en MIME-Version: 1.0 To: cocoon-dev@xml.apache.org Subject: Re: [RT] improving the session concept References: <3E91E9DB.6090807@apache.org> In-Reply-To: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N on 4/7/03 11:38 PM Pier Fumagalli wrote: > On 7/4/03 22:12, "Stefano Mazzocchi" wrote: > > >>The problem is that I'm pretty sure a lot of people simply won't call >>logout, so the session will expire and we'll left with the previous >>point (which makes it useless to even try the second). >> >>The really kick-ass thing would be to have a way to push an event >>listener into the session, that it gets called when the session expires. >> >>The problem is that the servlet API doesn't include this and there is no >>(portable) way to hook cocoon into the *real* session. > > > I don't understand what you're saying... Why can't we build the abstract > cocoon session code around javax.servlet.http.HttpSessionListener ? Ah, you're right. I overlooked that. Thanks for catching. -- Stefano.