Hi Felix! On Fri, Nov 21, 2008 at 8:16 AM, Felix Meschberger <[EMAIL PROTECTED]> wrote: > As a consequence the existing mechanisms would be dropped: > > VanityURLs : just set the URL on the "target" > URLMappings: just set the absolute path on the "target root" > Regexps : just set the respective mappings on the "target" > VirtualHost: just set the host on the "target root" > > The sole remains of existing mechanisms is the sling:vanityPath, which > is used as explained above.
Looks interesting! I am not familiar with the details of all existing mechanisms, but it seems that this is a nice simplification. It makes the whole config resource-based (since there are no globally configured mappings anymore), which - if there is a working cache - shouldn't have any disadvantages. BTW, how do I set vanity URLs in the current Sling? Do they allow sub-paths when compared to vanity paths, eg. if there is a sling:vanityPath = "/foo" set on /content/site/foo, will the request /foo/something be forwarded to /content/site/foo/something with vanity URLs? IIRC, this is not the case with vanity paths. Regards, Alex -- Alexander Klimetschek [EMAIL PROTECTED]
