[
https://issues.apache.org/jira/browse/SLING-848?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12670288#action_12670288
]
Tobias Bocanegra commented on SLING-848:
----------------------------------------
that's was i feared. using the ; parameters is not widely used, and causes
problems, as marc pointed out.
i think it's ok to use the parameters for the resource resolver - but then you
can also extend the api. i would avoid using them on the URI from the request,
especially, because the generation of such links is a bit special. i'd rather
see a "global" query parameter or cookie that controls the version selection.
> Support getting versioned resources by using uri path parameters
> ----------------------------------------------------------------
>
> Key: SLING-848
> URL: https://issues.apache.org/jira/browse/SLING-848
> Project: Sling
> Issue Type: New Feature
> Components: JCR Resource
> Affects Versions: JCR Resource 2.0.2
> Reporter: Carsten Ziegeler
>
> Getting versioned content should be support thorough uri path parameters,
> like /something/hello;v=1.1
> For jcr based resources the value of the version should either point to a
> version name or label.
> In order to not change our existing apis, we introduce a new utility method
> which removes all uri path parameters
> and returns a map of these. Every resource provider could use this utility
> method and then decide to act on these
> parameters.
> If a requested version does not exists, a 404 is returned.
> If the requested node does not directly point to a versionable node, the
> algorithm checks the parent hierarchy until a versionable node is found, and
> tries to get the version of this node and then goes down the path again. If
> the versionable node does not have the requested version or the child, a 404
> is returned.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
