RE: Last call: range locking
This is not the Versioning over HTTP group. This is the Distributed
Authoring AND Versioning over HTTP group. Distributed Authoring systems
have been using partial locks since their inception. Not only is new
ground not being broken, we are proposing not providing a feature that
has been universally provided in distributed/multi-user authoring
systems for decades.
>From: Christopher Seiwald [SMTP:email@example.com]
>Sent: Monday, March 03, 1997 9:18 PM
>To: Yaron Goland; firstname.lastname@example.org; email@example.com
>Subject: RE: Last call: range locking
>| Given that our goal is to provide for a distributed authoring and
>| versioning system that will be implemented (I mean it isn't like this is
>| our Phd. or something ;) and given that range locks are such a
>| fundamental feature that every major operating system, document creation
>| system, and database system provides them in one form or another, it
>| would seem that range locks are absolutely in scope.
>But few (no?) existing version control systems provide range locking.
>So you'd be breaking new ground -- not necessarily the best thing for
>a standards body.
>Christopher Seiwald Perforce Software 1-510-865-8720
>firstname.lastname@example.org f-f-f-fast SCM http://www.perforce.com