I'm not too familiar with the Tapestry pipeline/chain of command system which is why I chose to use a servlet filter. Other's might like to comment on the benefits of the Tapestry approach. It's certainly possible to cache on a page level using the servlet filter through the filter-mapping element.
As for authentication and cookie interception: I haven't done this myself because I use acegi, but acegi is basically a servlet filter which intercepts requests so I guess it must be possible! You may want to have a look at these excellent articles: http://www.onjava.com/pub/a/onjava/2003/11/19/filters.html?page=1 http://www.onjava.com/pub/a/onjava/2004/03/03/filters.html Toby 2008/8/27 codetester <[EMAIL PROTECTED]> > > Thanks Toby and others! > > Toby, is there a difference in using Servlet v/s tapestry filter for > caching > the page response? As in, is one of the method more preferred? Because, in > my case, I want to cache the response on certain pages like > www.myhost.com/category/cat1/ and not www.myhost.com/category/help etc . > > Also, is using T apestry filters the right way to port authentication and > cookie interceptor ( the current code that I have in struts ) ? > > Thanks! > > Toby Hobson-3 wrote: > > > > Tapestry 5 supports the url structure you mentioned using the "activation > > context". I'm not familiar with memcached but it is certainly possible to > > cache the entire page response using either a servlet or tapestry filter > > (i'm currently using a servlet filter for some high-load pages e.g. the > > home > > page) > > > > Toby > > > > 2008/8/26 codetester <[EMAIL PROTECTED]> > > > >> > >> Hi, > >> > >> I am new to Tapestry and trying to evaluate it for a personal project ( > I > >> am > >> current using struts2). Could someone help me in the following queries? > >> > >> 1) Is it possible to support the following URL structures out of the > box? > >> www.myhost.com/ > >> www.myhost.com/category/ > >> www.myhost.com/category/cat1/page1/xyz ... > >> > >> 2) Is is possible to conditionally plug in some cache ( like memcached > ), > >> so > >> that I can serve the entire processed HTML ( including the response > >> header > >> ) > >> directly to the servlet response stream? ( In case of a cache miss, then > >> the > >> normal flow would happen and I would conditionally cache the entire HTML > >> output ). > >> > >> Thanks! > >> -- > >> View this message in context: > >> > http://n2.nabble.com/Tapestry-query-on-URLs-and-Memcached-tp785361p785361.html > >> Sent from the Tapestry Users mailing list archive at Nabble.com. > >> > > > > > > -- > View this message in context: > http://n2.nabble.com/Tapestry-query-on-URLs-and-Memcached-tp785361p786126.html > Sent from the Tapestry Users mailing list archive at Nabble.com. > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > >
