> >As Garrett said, someday, after 1.0, we'll probably be
> >forced to implement some kind of locking, or a minimum,
> >a communication system which helps users discover
> >whether a file is being edited.
>
> File locking for the art stuff would be a major requirement for me.
Artists who 'check out' a working copy of a 3D model need to be sure that no
one is editing the same file. The 'notification' system that Karl Fogel
suggested in another thread doesn't seem like it would be suitable in this
case.
I was looking at
http://svnbook.red-bean.com/html-chunk/apds02.html#svn-app-d-sect2.3 and
there they mention that you can use mod_dav_lock (requires Apache 2.1+) to
handle locking files. Although the SVN specific client can break these
(with a SVN commit), but that seems to be a viable solution if normal uses
are using DAV and only admin users access the system via the SVN client.
Obviously it would be nicer to have consistent LOCK and UNLOCK, but I am
also pretty happy with the incremental change implementation ;-)
Don't know if that helps, but thought I'd mention it :-)
Z.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Mon Apr 28 12:44:01 2003