Any specifications would need to handle:

 *   node name collisions
 *   Valid version “discovery”
 *   “relative” versions (i.e. get the previous version)


From: Bruce Edge 
<bruce.e...@nextissuemedia.com<mailto:bruce.e...@nextissuemedia.com>>
Reply-To: "users@sling.apache.org<mailto:users@sling.apache.org>" 
<users@sling.apache.org<mailto:users@sling.apache.org>>
Date: Thursday, January 15, 2015 at 23:25
To: users <users@sling.apache.org<mailto:users@sling.apache.org>>
Subject: Re: Sling CRUD with content versioning, API architecture

Anyone interested in doing this for a bounty?

I¹ve filed a jira new feature req. SLING-4318 - Sling resource API does
not expose any versioning features. [1]
Please contact me directly if interested.

-Bruce

[1] <https://issues.apache.org/jira/browse/SLING-4318>



Thinking about this feature a little more. What would be involved in
making content versions accessible from WebDAV?
Is there any convention for mapping versioned nodes to a filesystem?

One mount point that represented all versions would be problematic because
whatever naming convention one came up with for representing versions
could collide with actual filenames.
Could one create a mount point for different versions? If one created
version labels at a specific node level, could those be used as mount
points to access that version of the content as read/only data?

-Bruce



________________________________
This E-mail and any of its attachments may contain Time Warner Cable 
proprietary information, which is privileged, confidential, or subject to 
copyright belonging to Time Warner Cable. This E-mail is intended solely for 
the use of the individual or entity to which it is addressed. If you are not 
the intended recipient of this E-mail, you are hereby notified that any 
dissemination, distribution, copying, or action taken in relation to the 
contents of and attachments to this E-mail is strictly prohibited and may be 
unlawful. If you have received this E-mail in error, please notify the sender 
immediately and permanently delete the original and any copy of this E-mail and 
any printout.

Reply via email to