----- Original Message ----- From: "Gianugo Rabellino" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Sunday, May 26, 2002 8:37 AM Subject: [VOTE] Adding "Expires" headers to pipelines
> > After a long period of inactivity I was able to spend some time on > Cocoon in this weekend. I must confess that I'm really impressed with > the work going on so far: Schecooon, XMLForm, Treeprocessor and so on > are making Cocoon plans for world domination much closer to reality :-) > Thanks to everyone for this wonderful software! > > Now for the [VOTE] I'm calling. I'm recalling here the thread that I > launched some time ago about cache friendly HTTP headers (see > http://marc.theaimsgroup.com/?t=101074439900001&r=1&w=2 for details). I > have a working[1] version sitting on my hard drive of a sitemap > extension which allows to set custom "Expires" headers for every > pipeline. The syntax (and functionality, and scope...) is compatible > with Apache's mod_expires (see > http://httpd.apache.org/docs/mod/mod_expires.html) from which the idea > was stolen. With this modification you can configure a sitemap as follows: > <snip/> > > 1. Would you like this addition to be committed to HEAD? If so I promise > to come up with documentations and a short HOWTO on how to connect a > reverse proxy with Cocoon. +1 Is it possible that this is used in some fashion for dynamic pages as well? In some cases the Action or Generator would have information as to whether the underlying data model has changed and so they can in turn decide to invalidate the cache. > > 2. Would you like the "expires" settings to be available in the current > ObjectModel so that the cache might become aware of it? +1 And to answer the issue of TreeProcessor vs Compiled, I guess I'd vote for 1) (keep TP only) unless someone can demonstrate severe performance constraints. Ivelin > > Ciao, > > -- > Gianugo Rabellino > > 1: well... almost: I need to understand some TreeProcessor quirks to see > if I'm doing something wrong or if some exceptions I'm getting - while > the setup is working - are normal > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, email: [EMAIL PROTECTED] > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
