multiple users at the same time on one repo...

[Robey Pointer]

On 21 Aug 2006, at 13:19, John Arbash Meinel wrote:

> Erik Bågfors wrote:
>>
>> The situation that I'd love to see is to replace svn with bzr but
>> still allow people to work the same way (in a centralized manner).
>> That would mean that many developers are using checkouts on multiple
>> branches in that same repo at the same time.
>>
>> I think that locking will become a serious problem then.   I haven't
>> tried to do this yet, but it should be fairly easy to test what
>> happens.
>
> There are a few possibilities.
>
> [...]
>
> 2) It is already possible to wait on a lock for a short period of  
> time.
> We just need to update the code so that it doesn't always puke right
> away, but is given the opportunity to wait for a few seconds before
> failing. This mostly has implications based on how long a lock is
> expected to be held versus the frequency of commits.

This is what perforce does, though I don't think it has a timeout.   
You can just hit ^C to give up.  Our perforce server at work can  
occasionally get very congested and 10 seconds wouldn't be nearly  
long enough.  It's possible that bzr could have the same problem over  
a high-latency link.

robey