Re: file locking and binary files

Ben Collins-Sussman wrote:

>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.

I'm joining in this discussion a bit late, but one message suggested to do so if the issue was important to us.

I'm currently in the planning stages of a in-house tool for game development which would emulate the functionality of AlienBrain (www.alienbrain.com) which I have heard horror stories about.

Subversion seems like a great candidate for the underlying system, all I'd have to program is the Maya/3DStudio/Photoshop integration for the art side.

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 could go around this issue by creating a thin layer sql database which would provide the locking mechanism for art file (as long as they are accessed thru the integration plugins) and that would be fine for my uses.

Anyway, just curious to know if I'm wrong in my assesment that the 'watcher' daemon wouldn't work for my case, and wether maybe both type of locking could be available (daemon based and real locking) in a post-1.0 release.

And, BTW, great app! Keep up the good work!
-D

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Mon Apr 28 07:05:47 2003