Your second method
http://www.foo.com/index-xyz.html
still forces the designer to know parameters when he/she creates a
link. But I think first method is useful.
http://www.foo.com/xyz/index.html
May you give me a tip about how to parse these parameters to use in
XSL stylesheets? Can Cocoon
Change that to http://www.foo.com/x/y/z/index.html and you can use a
pipeline matcher like this:
map:match pattern=/*/*/*/*.html
map:generate src=/docs/{4}.xml/
map:transform src=/styles/yourtransfomer.xsl
map:parameter name=x value={1}/
map:parameter name=y value={2}/
At 13:33 14/05/2002, you wrote:
Change that to http://www.foo.com/x/y/z/index.html and you can use a
pipeline matcher like this:
map:match pattern=/*/*/*/*.html
map:generate src=/docs/{4}.xml/
map:transform src=/styles/yourtransfomer.xsl
map:parameter name=x value={1}/