Tapestry maintains an illusion that there's a direct connection between individual users and particular page instances ... but its really a shell game. Persistent properties (marked with the @Persist annotation) have their values stored in the HttpSession between requests. On each request, an *equivalent* (but not identical) page object is obtained from the pool, and has its properites rewound from data in the HttpSession.
At the end of the request, all transient and persistent properties are reset to default values and the page goes back into the pool for later reuse by the same, or different, client. All the business with abstract properties and such is so that Tapestry can write the tedious code that manages those properties, including various kinds of notifications and cleanups. On 11/22/05, Cosmin Bucur <[EMAIL PROTECTED]> wrote: > I wanted to know if there's a pool of page objects which are used whenevevr > needed , or if , when a page object is accesed by a user , it gets > associated with that user's session on the server , therefore variables > stored by the user on a page would be available to the user later through > that same page ? > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > -- Howard M. Lewis Ship Independent J2EE / Open-Source Java Consultant Creator, Jakarta Tapestry Creator, Jakarta HiveMind Professional Tapestry training, mentoring, support and project work. http://howardlewisship.com --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
