tapestry-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jamie Orchard-Hays" <ja...@dang.com>
Subject Re: [Jakarta Tapestry Wiki] Updated: Tapestry31Status
Date Tue, 09 Nov 2004 22:34:15 GMT
Is having data persist only per page difficult? This would be the default 
usage and probably apply to 95% of situations.

Jamie
----- Original Message ----- 
From: "Howard Lewis Ship" <hlship@gmail.com>
To: "Jamie Orchard-Hays" <jamie@dang.com>; "Tapestry development" 
<tapestry-dev@jakarta.apache.org>
Sent: Tuesday, November 09, 2004 4:14 PM
Subject: Re: [Jakarta Tapestry Wiki] Updated: Tapestry31Status


> The problem is coming up with hard rules for when you can discard
> data, mated to some simple syntax for expressing it!
>
>
> On Tue, 9 Nov 2004 12:26:00 -0500, Jamie Orchard-Hays <jamie@dang.com> 
> wrote:
>> I like the direction you're heading with this. Cookie, q param and form
>> fields are all valid ways of persisting and having an automatic way would 
>> be
>> great.
>>
>> Having duration would also solve a lot of problems and/or code verbosity
>> I've encountered with having persistence that I don't want hanging around
>> when I'm done with the data. Having a persistence mode or duration that 
>> only
>> lasted while returning to the same page and then discard after would be a
>> big plus. It would mean less manual coding to clean up data from memory 
>> when
>> leaving a page and would take care of those cases when you can't clean it
>> out (ie, user wanders off via a link to some other part of the app).
>>
>> Jamie
>>
>>
>>


---------------------------------------------------------------------
To unsubscribe, e-mail: tapestry-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tapestry-dev-help@jakarta.apache.org


Mime
View raw message