gt; >> 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 t
g 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
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/
L ( 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.nab
A caching filter should have nothing to do with Tapestry, as long as you
set the Expires headers properly. To that end, I don't believe tapestry
has any support for caching built in.
Though there is no general caching filter backed by memcache, you could
look at Ehcache's implementation of ca
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.
