On Dec 10, 2007 12:25 PM, Juan José Vázquez Delgado <[EMAIL PROTECTED]> wrote:
> > (1) encode the requested version as part of the URL, such as > > /content/some/resource.html;v=1.0 (for the resolve(request) method)... > > ...IMHO, there are some situations which we can need to retrieve the same > resource based on a particular perspective: version, language, anything > else? I think that's what selectors are for - maybe we need to reserve some of the selector "namespace" for sling-specific stuff? For example /content/mytext.a4.print.s:version:1:4.s:locale:fr_CH.html would mean resource path = /content/mytext application selectors = a4.print version = 1.4 locale = fr_CH output format = html As you mention, requesting a version in this way would need encoding the dots in version numbers as colons, as dots separate selectors. Do people think we need a syntax for selectors that are handled by the Sling/microsling framework and not by applications? -Bertrand
