hi,
On Mon, 4 Nov 2002 22:30:25 +0000, "Luis Neves" <[EMAIL PROTECTED]> said:
>
> I guess I'm just suffering from "penis envy", the JSP folks have OSCache
> and the ASP.NET folks also have a great caching service and I wanted some of
> that to :-)
>
> I'm a huge Tapestry fan but sometimes I can identify with the quote that
> someone made a while ago:
> "Tapestry makes hard things easy and easy things hard"
> Things like caching the response output or changing the response
> content-type shouldn't be so complicated.
the trouble is, that the "simple" caching provided by OSCache for
example, is really not that simple - you are making the same tradeoffs as
you would in tapestry... for example: you can run into trouble with users
who don't have cookies enabled (-> url rewriting), but then if you make
the full url the key, caching suffers, since you start to cache things on
a per-session basis, which is probably not what you wanted anyway...
also, the same problems exists there with caching dynamic content, eg. if
the cached region has anything that would set up a variable, attribute,
etc. that will not be executed...
so to sum it up, caching html is no less problematic in tapestry that it
is in the JSP world, although you dont get the tool to shoot yourself in
the foot out of the box :))
best regards,
viktor
--
[EMAIL PROTECTED]
--
http://fastmail.fm - Sent 0.000002 seconds ago
-------------------------------------------------------
This SF.net email is sponsored by: ApacheCon, November 18-21 in
Las Vegas (supported by COMDEX), the only Apache event to be
fully supported by the ASF. http://www.apachecon.com
_______________________________________________
Tapestry-developer mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/tapestry-developer
