"Phil Harris" <phil.harris@zope.co.uk> writes:
Might be a good sart for you and they should have something soon.
The webdav faq says: For now and for a while, CVS will still be your best bet; it is going to be a while before DAV's versioning capabilities match that of CVS. This has been the status for quite a while. What would it take to add interim CVS functionality into zope ? I mean just the most useful bare essentials - - storing & retrieving past versions - talking to standard cvs tools via the pserver protocol Enough to support, eg - cvs checkout - cvs update - cvs commit - cvs diff - cvs status Vague strategy #2.1: 1. create a ZCVSAware mixin class, which hooks into standard zope objects' get & set methods. A ZCVSAware object stores past revisions of its data and can provide a specified revision on request. This is separate from zope's undo mechanism. 2. add a pserver protocol handler to zserver Cheers and a happy new millenium to all, -Simon