On Fri, 10 Jan 2003, Bruce Robertson wrote: <snip/>
> Hooray, we're caching this css file on the client for a few hours! > > This approach has one advantage over setting the expire within cocoon > itself. Client-side caching gets in the way of development, where one > wishes immediately to see the results of changes in code. As it stands, > my webapp is distibuted without c-s caching, so interested parties can > fiddle with it, but once installed in the project's main server the > webapp's content is automagically client-side cached. Bruce, This is a very very nice writeup! Would you mind wiki-fying it over at http://wiki.cocoondev.org/ ? Stuff like this needs to get assimilated into the docs. Regards, Tony --------------------------------------------------------------------- Please check that your question has not already been answered in the FAQ before posting. <http://xml.apache.org/cocoon/faq/index.html> To unsubscribe, e-mail: <[EMAIL PROTECTED]> For additional commands, e-mail: <[EMAIL PROTECTED]>
