Re: Sling CRUD with content versioning, API architecture

Why not using selectors in combination with a suffix? GET information about existing versions /path/to/resource.versions.json GET a version /path/to/resource.versions.json/versionA.json POST to create a version /path/to/resource.versions.ext But nevertheless this improvement sounds quite intere

RE: Sling CRUD with content versioning, API architecture

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 als

Re: Sling CRUD with content versioning, API architecture

Any specifications would need to handle: * node name collisions * Valid version “discovery” * “relative” versions (i.e. get the previous version) From: Bruce Edge mailto:bruce.e...@nextissuemedia.com>> Reply-To: "users@sling.apache.org" mailto:users@slin

Bounties for developers (was: Sling CRUD with content versioning...)

On Thu, Jan 15, 2015 at 11:24 PM, Bruce Edge wrote: > ...Anyone interested in doing this for a bounty?... FWIW if this happens (which would be very cool) http://community.apache.org/committers/funding-disclaimer.html has relevant information about how bounties can work w.r.t the Apache independen