- From: Clemm, Geoff <gclemm@rational.com>
- Date: Thu, 12 Jul 2001 16:07:51 -0400
- To: DeltaV <ietf-dav-versioning@w3.org>
The resolution I recorded was that DeltaV would remain silent until the status of lock null resources was resolved by the WebDAV working group. The most recent word on this in the WebDAV mailing list was: ---------------------------------------------------------------------------- - DEFER_LOCK_NULL_RESOURCES_IN_SPEC Proposal to remove lock null resources from the spec until we are motivated to have them or something equivalent. In the meantime, keep the spec silent on the topic in order to avoid precluding LNR or the equivalent in a future version of WebDAV. ------------------------------------------------------------------ To me, this supports the current resolution to remain silent in the DeltaV draft on the topic of lock null resources. Cheers, Geoff -----Original Message----- From: Lisa Dusseault [mailto:lisa@xythos.com] Sent: Thursday, July 12, 2001 12:28 AM To: DeltaV Subject: Versioning and Lock Null resources I haven't seen a resolution to DeltaV's lock null resource issues. Can a client issue the following requests on a lock null resource: - VERSION-CONTROL - MKACTIVITY - MKWORKSPACE - BASELINE-CONTROL Specifically, one might imagine a client trying to create a new versionable resource and work with it by attempting the following sequence: LOCK, VERSION-CONTROL, CHECKOUT, PUT (etc), CHECKIN, UNLOCK Lisa
Received on Thursday, 12 July 2001 16:00:30 UTC