On Dec 12, 2007, at 1:10 PM, Bertrand Delacretaz wrote:
How about
/content/some/resource.html/s:version:1.4/s:lang:fr/somefile.pdf
where suffixes starting with s: are reserved for Sling usage?
yuck. A general principle of web design is that you shouldn't
be able to tell how a server is implemented by looking at the URI,
because that means the URIs will break when the implementation
is changed. A corollary is that any new web framework should be
able to adopt any existing set of resources, without the user
being aware of it and without changing the cool URIs.
What we should do is separate the mapping into a sequence
of extensibility hooks and only define the delegation points.
For example, we know that the path up to the last JCR node
is handled by Sling, so just define everything after that
point (i.e., EXTRA_PATH) as input to a sequence of registered
filters for that resource (where the sequence is itself a
node identified by a property on the resource node, either
explicitly or by default based on node type). That would
allow both fine-grained handling of the extra path and
flexibility for legacy resources.
BTW, I find the "/content" prefix really annoying. Does anyone
(aside from day.com) do that in real life? Most sites use virtual
hosts for that type of separation, or at least very short roots.
....Roy
