On Mon, Jan 6, 2014 at 3:00 PM, Justin Edelson <[email protected]> wrote: > ...My personal opinion is that supporting 10k vanity paths is a non-goal, > but that's just me :)...
I would agree but users are creative sometimes ;-) Worst case, we might provide a way to disable the default vanity paths handling completely and let people implement their own variant, for exotic use cases. > ...I believe Felix has proposed a solution to "migrate" vanity paths from > wherever they are defined into /etc/map through some kind of approval > workflow. Search the list archives for more details.... I remember these discussions but haven't followed in detail. Looking at this I tried to list all the ways that we have to map incoming URLs to resources and vice-versa, and it makes me wonder if we really need all these mechanisms: a) Vanity URLs, sling:vanityPath http://sling.apache.org/old-stuff/request-processing.html b) Mappings via /etc/map with sling:match, sling:alias, sling:internalRedirect, sling:redirect http://sling.apache.org/documentation/the-sling-engine/mappings-for-resource-resolution.html c) sling:alias and sling:redirect on any resource Documented a the same URL as b) d) Resource resolver virtual URLs No docs? e) Resource resolver URL mappings No docs? f) Resource resolver namespace mangling No docs? Not sure if this list is even complete... -Bertrand
