On 4/6/07, Henry S. Thompson <ht@inf.ed.ac.uk> wrote: > > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > Alex Milowski writes: > > > While caching has been declared dead, this is a great solution > > for a user of a pipeline in that they can run two separate pipelines. > > One produces a set of documents that are put into the catalog > > or cache and the second uses that cache via an implementation > > defined feature. > > Don't agree -- still wouldn't work for Richard, as I understand his > objection (consider again the stylesheet with an xsl:include), and if > it _would_ work, however it would work would be appropriate for > 'fixing' my proposal to add a 'cache' port to p:group. Applications cache "GET" requests on http urls all the time. I can't see how we can disallow an implementation from allowing a user that option when they deploy their pipeline. -- --Alex Milowski "The excellence of grammar as a guide is proportional to the paucity of the inflexions, i.e. to the degree of analysis effected by the language considered." Bertrand Russell in a footnote of Principles of MathematicsReceived on Saturday, 7 April 2007 17:17:50 GMT
This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 8 January 2008 14:21:50 GMT