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. >
