deelan [mailto:deelan@...] wrote:
> yes, this is the issue i wanted to point out with my post.
> after "index" servlet everything is fictional: "param1" and "param2"
> are just used to make the URL more friendly, so instead of write:
> you reduce the url to:
> resources (images, CSS) should looked up after the context:
Of course, Webware does know where the context starts, but unfortunately =
doesn't know where the extra parameters end. Therefore, you really need =
kind of "base" element in your HTML to avoid the confusion.
> however i think i'll drop extrapathinfo, given its current state
> it's too much tricky to get everything right. i'm gonna
> investigate apache's mod_rewrite and possibly generate static
> HTML pages upon request.
One thing that I forgot to mention was that in Apache Cocoon =
framework), there are various pattern matching features which can be =
detect things like "all files ending with .css", and whilst one can take =
simplistic approach and divert accesses to such resources to a single =
directory of such files, usually that's good enough. In other words, =
rare to have hierarchies of stylesheets, in my experience, and so you =
put them all in one place and let the framework find them there when it =
one of them mentioned anywhere in the URL.
So with mod_rewrite, which is probably even more powerful, you could
certainly consider retaining extrapathinfo and introduce pattern =
for those special "diversions" to common directories. For example:
This would cause the Apache to realise that a stylesheet is being =
and just serve up that document from some directory, rather than having
Webware trying to work out whether styles.css is dynamic content, an
argument or whether a servlet should be invoked or not.
Hope that made sense!