On Monday, 27. January 2003 19:33, Robin Berjon wrote: > Jörg Walter wrote: > > Moreover, AxOutputTransformer was designed to be _behind_ the cache. This > > patch puts it before the cache. If it is used for anything cacheable, > > it's purpose wasn't understood. > > Not commenting on the patch (which I haven't reviewed sufficiently > closely), Matt and I discussed the position of OutputTransformers relative > to caching not long after it went in. There are of course good reasons to > put it after the cache but there are many cases in which it doesn't make > much sense. For instance, given char transcoding at the end of the pipeline > (it's implemented as an OutputTransformer) it's a bit silly to perform > UTF-8 => Latin-0 conversions for each hit on cached data :)
Well, this is more of a design fault in that char transcoding you are talking of. Without OutputTransformers as we have it now it would be impossible to have ad banners on every page unless you switch caching off entirely. > The conclusion was that there was indeed some value in having > AxPreCacheOutputTransformer and AxPostCacheOutputTransformer but neither of > us had the tuits or sufficiently felt the itch for that to happen back > then. Why have an AxPreCacheOutputTransformer? Why not add another stylesheet? After all, they are the ones doing regular transformation. That charset thingy could register itself as a special kind of stylesheet that only works at the end, just like other language modules we have, HtmlDoc for example. -- CU Joerg PGP Public Key at http://ich.bin.kein.hoschi.de/~trouble/public_key.asc PGP Key fingerprint = D34F 57C4 99D8 8F16 E16E 7779 CDDC 41A4 4C48 6F94
