- From: Rick Rupp <rick.rupp@merant.com>
- Date: Wed, 20 Jun 2001 17:30:17 -0700
- To: <ietf-dav-versioning@w3.org>
The idea proposed by Tim concerning a new CHECKIN option to replace what is trying to be done with DAV:checked-out-vcr seems good. This allows a client to request the server to do the checkin/update operations and not require it to be done. I am not convinced that servers supporting other core versioning features should be required in all cases to update the VCR on check in. If the DAV:checked-out-vcr property is made part of the specification then I would prefer it to be OPTIONAL and not REQUIRED. I'm also wondering if a new core versioning package shouldn't be described similar to the basic-client-workspace package without the update and label features. At 02:45 PM 6/20/01 +0100, Tim Ellison wrote: >John Hall wrote: > > In my system I have no problem tracking moves, but it isn't my > > objective. My objective is having a CHECKIN of the working resource > > update the VCR. That isn't a 'gee it would be nice to have' request. > > It is far more important to me than that. Lack of such a feature would > > be quite painful. > >I think you may have said this already, so apologies if you did. Instead of >a new property on a working resource that tracks MOVEs (which I think will >be hard to implement on distributed systems), how about a new CHECKIN option >to do the checkin and version-controlled resource update atomically with a >specific error condition if either cannot be achieved? > >I'd be happier with that. > >Tim
Received on Wednesday, 20 June 2001 20:31:43 UTC