I was wondering about the rational for using parameters to display the version rather than using a selector. I would have thought a selector would be more inline (with my understanding) of using selectors to depict a variant of what the full path represents.
If this is implemented. We would also need controls to disable. We have pages that we have no desire for external visitors to see prior versions. -----Original Message----- From: Felix Meschberger [mailto:[email protected]] Sent: Thursday, January 15, 2015 10:23 AM To: <[email protected]> Subject: Re: Sling CRUD with content versioning, API architecture Hi We once discussed using path parameters for that, For example /some/resource;v=123 to select version 123. The JCR Resource Provider would have to be adapted for this. Depending on how we combine this with selectors and extensions the ResourceResolver as well. For the update, the POST servlet has support to create versions. There is no Resource based API for this, though. Regards Felix -- Typos caused by my iPhone > Am 15.01.2015 um 16:08 schrieb Bertrand Delacretaz <[email protected]>: > >> On Thu, Jan 15, 2015 at 3:38 PM, Robert Munteanu <[email protected]> wrote: >> ...You _might_ be able to get away with creating a new resource >> provider, based on the jcr resource provider.... > > And if needed combine this with a set of selector-driven servlets. > POST to foo.V to create a version, GET foo.V.json to list them, etc. > > This comes up from time to time but for some reason it seems like no > one needed this enough to implement it so far. But that would be a > good addition to Sling IMO. > > -Bertrand
