Hi James,
As the others have said, there is no way with the servlet spec to use
the servlet session mechanism in the fashion you want. So, one solution
is for you to manage sessions yourself.
At the end of the day, all you need to recognise a request from any
given browser is a cookie. Long time since I did T3 stuff, but I would
suggest you create your own cookie representing a session, and use that
as a key to lookup any session data you need, and not use the standard
Tapestry session mechanisms that are built ontop of the Java servlet
session cookie.
Richard
James Sherwood wrote:
So there is no way to have it last the length of the browser being open?
I have seen tricks using JavaScript to contact images and such to keep
sessions alive.
--James
----- Original Message ----- From: "Thiago HP" <[EMAIL PROTECTED]>
To: "Tapestry users" <users@tapestry.apache.org>
Sent: Tuesday, December 04, 2007 11:57 AM
Subject: Re: T3: session length
On 12/4/07, James Sherwood <[EMAIL PROTECTED]> wrote:
What is the downfall to this?
Each user session will last forerever even when the user is not using
the
application, leading to an always increasing server memory usage. Of
course
you could release the session (session.invalidate()), but I don't
think it's
your case.
Thiago
__________ NOD32 2701 (20071204) Information __________
This message was checked by NOD32 antivirus system.
http://www.eset.com
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--
Richard Kirby
Email: [EMAIL PROTECTED]
Phone: 0131 477 8629
Fax: 0131 477 8621
Email: [EMAIL PROTECTED]
Website: www.capdm.com
CAPDM Limited Registered in Scotland: SC168970 VAT: 682 846 983
Registered address: 22 Forth Street, Edinburgh, EH1 3LH, UK
===========================================
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
