Hi, > (1) encode the requested version as part of the URL, such as > /content/some/resource.html;v=1.0 (for the resolve(request) method)
I like this solution but why not to use Sling api standars like selectors or suffixes? Really, the selectors have a problem with the dot character... I´m not sure about the second and third propossals. I think this sort of issue, like the version one, is not an isolated issue. For instance, what about a resource with several translations?. IMHO, there are some situations which we can need to retrieve the same resource based on a particular perspective: version, language, anything else? BR, Juanjo On Dec 10, 2007 11:07 AM, Felix Meschberger <[EMAIL PROTECTED]> wrote: > Hi Juanjo, > > This is a very good question, we deliberatly did not touch yet. But you > are of course right, we probably need something like this. Out of my > belly, I would think of the following: > > (1) encode the requested version as part of the URL, such as > > /content/some/resource.html;v=1.0 (for the resolve(request) method) > > The value of the v parameter is the version label. > > (2) add getResource parameters with an additional version label > parameter: > > ResourceResolver.getResource(String path, String versionLabel); > > (3) add support for a well-known HTTP header and/or parameter for the > ResourceResolver.resolve(request) method. > > WDYT ? > > Regards > Felix > > Am Montag, den 10.12.2007, 11:00 +0100 schrieb Juanjo Vázquez: > > Hi all, > > > > I don´nt know if anyone has thought in this scenario: to retrieve a > resource > > based on a particular version of a node instead of the head version. > > > > WDYT? > > > > Regards, > > > > Juanjo. > >
