Lutz, Thanks for the response - Cookies would be a last resort - I don't want to be managing cookies and also feel it makes the app more breakable (fundamental state could be broken with browser security settings). What I'm after is something akin to PageActivationContext but that passes the relevant object(s) using Request parameters rather than the querystring / url - thanks.
Regards, Jim. -----Original Message----- From: Lutz Hühnken [mailto:lh.tapestry.l...@googlemail.com] Sent: 06 January 2010 13:50 To: Tapestry users Subject: Re: Persisting state without HTTP Session Cookies come to mind, would that be an option? On Wed, Jan 6, 2010 at 2:16 PM, Jim O'Callaghan <jc1000...@yahoo.co.uk> wrote: > Hi, > > Can anyone advise on the preferred way of persisting state between pages > without using HTTP Session? PageActivationContext using Object[] looks > promising but I don't want long urls (from serialized objects) and there is > more data to share than a defined number of keys - I'm looking for something > that uses POST params ...? Thanks. > > Regards, > Jim. > -- altocon GmbH http://www.altocon.de/ Software Development, Consulting Hamburg, Germany --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
