Hi,
some interesting and insightful information here. Thank you for that!
Regards,
Daniel P.
-Ursprüngliche Nachricht-
Von: Thiago H de Paula Figueiredo [mailto:thiag...@gmail.com]
Gesendet: Mittwoch, 18. März 2015 14:07
An: Tapestry users
Betreff: Re: AW: Memory Footprint in Tapestry
Hi,
yes, I've read http://tapestry.apache.org/persistent-page-data.html. I just
couldn't wrap my head around it before because I always thought storing data
between requests automatically meant storing it in a client-side cookie or
something like that. This has been cleared up, thank you for th
On Wed, 18 Mar 2015 07:32:43 -0300, Poggenpohl, Daniel
wrote:
Hello,
Hi!
from what I gather, Tapestry intercepts requests and looks for the
according page instances in the server-side application.
Correct, as Tapestry is implemented as a servlet filter, not a servlet, so
"interceptin
Hello,
from what I gather, Tapestry intercepts requests and looks for the according
page instances in the server-side application. The session id, if present, is
transmitted with the request, so the appropriate page instance is used that
maybe has some session-@Persist'ed members. Java code is
