hi everyone!
for 1.4.1, i would like to propose a huge refactoring of lenya's pipelines and URL handling. first, there is obviously way too much boilerplate stuff in the publication's sitemap.xmap. essential features like link rewriting, gui styling and cache writing should be handled by the core or by appropriate modules. plus we need to rethink the way we handle URLs. two important issues surfaced during my attempts to fix our proxying: * all internal URLs in lenya should disregard any proxy or context prefixes * we need *one* central post-processing pipeline that will get to see *all* requests. this pipeline can then rewrite links according to proxy settings and webapp context. this includes pipelines for css and all other file formats that allow referencing of other documents (such as rng includes, should we ever use client-side validation). these changes will help to centralize the knowledge about contexts and proxy directories, and will do away with the many stupid "forgotten context" mistakes we keep making, for good. *.* when we rewrite our sitemaps, we can make them more caching-friendly as well. i believe that cleaner pipelines and some thinking about cocoon's generic caching mechanism can help a lot to alleviate the performance problems that users have reported. (that would also include migrating from the CIncludeTransformer to the IncludeTransformer, which supports caching). there was a rather clueful talk about caching at cocoongt 2006: http://wiki.apache.org/cocoon-data/attachments/GT2006Notes/attachments/10-caching.pdf wdyt? -- Jörn Nettingsmeier Kurt is up in heaven now. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
