On Wednesday 26 March 2008 14:26:34 Patrick Heiden wrote: > Vadim Gritsenko wrote: > > And downside is polluted cache and proxies.
Yeah, and the general evilness of URI Aliasing: http://www.w3.org/TR/webarch/#uri-aliases > > It's much better to just parameterize XSLT with absolute context path, > > or with relative path to the context root. Better yet is to move > > static resources out to httpd server. Is the way of doing that in 2.1 still valid for 2.2? We found only http://cocoon.apache.org/2.1/apidocs/org/apache/cocoon/components/modules/input/ContextPathModule.html > Well, that is right, but what should one do inside development-environment > where there is no such httpd? Come to think of it, is it possible, or rather, is it easy, to get the context into the hostname part of the URL rather than the path? That could potentially ease many of these problems. Kind regards Kjetil Kjernsmo -- Senior Knowledge Engineer Direct: +47 6783 1136 | Mobile: +47 986 48 234 Email: [EMAIL PROTECTED] Web: http://www.computas.com/ | SHARE YOUR KNOWLEDGE | Computas AS Vollsveien 9, PO Box 482, N-1327 Lysaker | Phone:+47 6783 1000 | Fax:+47 6783 1001 --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
