Yes, Tapestry pools the pages, so only a single thread (processing a single request) will have access to a page instance. This allows the pages to be trully stateful ... for the duration of a request. All the business about abstract properties is really about Tapestry propertly cleaning up the page before returning it to the page pool, at the end of the request.
On 12/8/05, karthik G <[EMAIL PROTECTED]> wrote: > Hi All, > > At any point of time , would it be correct to say that only one user thread > will be executing a Page instance? I understand that another thread might > get to the same instance later. Does tapestry4 Page instance behave like > Stateless Session Bean instances?. Please explain this part as it will help > me make certain assumptions when working with tapestry4. > > thanks, > karthik > > -- 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]
