> > I suppose your page implements IExternalPage? > > You mean that I create a single Tapestry class implementing > IExternalPage, right? All my (variably many) pages use this > class. Correct?
Yes. > > > If you seed you page/app with external parameters which you > need later > > on, in subsequent requests, store them in page/component properties > > marked as @Persist-ent. > > Does this mean that Tapestry will keep in its page pool an > IExternalPage page for each article I have in the DB (once > this page is visited)? Please refer to http://tapestry.apache.org/tapestry4.1/usersguide/state.html Tapestry will keep in its pool one instance for each *concurrent request* it is serving. Your persistent page-id will be stored in the session or on the client (configurable). When a request comes in, Tapestry will pick a page from the pool and provide it with the persistent property data, e.g. the reference to your db-data. > > Is this a good idea? I have lots of pages and at some point, > the memory might be full. Or is there some mechanism that > purges pages from the cache? > > I am sorry if my questions are quite basic! The more I > appreciate your help. > > Kaspar > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
