[
https://issues.apache.org/jira/browse/SLING-848?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12670273#action_12670273
]
Bertrand Delacretaz commented on SLING-848:
-------------------------------------------
I think
/content/home/tobi.html;v=1.5
breaks existing logic, as IMHO programmers assume that things that affect the
representation come at the end of the URL.
I much prefer
/content/home/tobi;v=1.5.selector.html
Where the URI parameters (which affect the selected content) come first, and
the selectors and extensions (which affect the representation) last.
Also, why not change the API? If we start supporting URI parameters as
specified, the least surprising way would be to add a (backwards-compatible)
getURIParameters method to the SlingHttpServletRequest interface. Hacking the
content path downstream feels wrong.
> 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.
