I'd encourage you to use Delta-V. It already allows for resources
"normally" not being under version control, and a "new command" (the
VERSION-CONTROL method) to bring a resource under version-control.
There is also provision for auto-versioning based on modification and,
optionally, lock state transition.
A server is only required to implement basic versioning to be Delta-V
compliant -- indeed there will be very few, if any, servers implementing
the entire specification. The working group have tried to reduce the basic
versioning functionality to the minimum coherent set of behavior that is
useful and consistent with the extensions added by advanced versioning.
If there is some more fundamental set of services that you can imagine then
please send in your suggestions. I hope there is no room for new
"compatible" commands.
Regards,
Tim
"Pill, Juergen" <[EMAIL PROTECTED]> wrote:
>
> Hello,
>
> what do you think about, that Slide "normally" will not
> using versioning, but we will implement a new command, which
> puts a resource under version control. From this point on,
> slide creates a new version each time a put/unlock is performed.
> Possibly some other version control commands could be implemented
> in a light weight fasion to allow a reasonable amount of versioning
> (without the full blown DELTA-V standard). Anyway I believe these
> new commands should be compatible with deta-v.
>
> Best regards
>
> Juergen Pill
>
> -----Original Message-----
> From: Remy Maucherat [mailto:[EMAIL PROTECTED]]
> Sent: Tuesday, May 29, 2001 19:30
> To: [EMAIL PROTECTED]
> Subject: Re: Versioning - like CVS) with slide
>
>
> > "Remy Maucherat" <[EMAIL PROTECTED]> wrote:
> > > > Dear list ...
> > > >
> > > At some point, the WebdavServlet was doing automatic versioning (ie,
> when
> > > you do a PUT, it stores the content in a new revision).
> > > It doesn't do this anymore, for a variety of reasons, the main one
being
> > > that Delta V mandates that no automatic versioning should happen by
> > default.
>
> Tim Ellison wrote:
> > Automatic versioning by servers is permitted by Delta-V.
> > See draft-ietf-deltav-versioning-15, Section 2.2.1
> >
> > "Normally, a resource is placed under version control with an
> > explicit VERSION-CONTROL request. A server MAY automatically
> > place every new versionable resource under version control.
> > In this case, the resulting state on the server MUST be the
> > same as if the client had explicitly applied a VERSION-CONTROL
> > request to the versionable resource."
>
> Thanks for the info.
> I could be wrong, but I don't think that was the case with the older
drafts.
>
> Remy
>
