[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: Locking by default

From: Branko Cibej <brane_at_xbc.nu>
Date: Fri, 06 Feb 2009 04:32:57 +0100

Luca Arzeni wrote:
> "Branko Čibej" wrote:
> > What kind of heavy burden would that be, exactly?
>
> In our understanding, on each file that we will submit, snv will need
> to execute a query to look for prop svn:needs-lock.
> Also, it will need to manage an attribute more for every file in the
> repository.

Ok, so apart from following Ben's advice, how about actually doing some
performance measurements to compare the two models before proposing code
changes? Quite possibly the differences are not important.

It's more likely that you'll see bigger losses of productivity from all
the developers waiting for others to unlock files.

-- Brane

>
> Regards, larzeni
>
>
>
> ----- Original Message -----
> From: "Branko Čibej"
> To: larzeni
> Cc: dev_at_subversion.tigris.org
> Subject: Re: Locking by default
> Date: Tue, 03 Feb 2009 16:44:23 +0100
>
>
> larzeni wrote:
> > |Since we are going to use almost on all files |the
> lock/modify/unlock
> > model, we fear that we will impose a heavy burden on the server.
>
> What kind of heavy burden would that be, exactly?
>
> -- Brane
>
>
> --
> Be Yourself @ mail.com!
> Choose From 200+ Email Addresses
> Get a *Free* Account at www.mail.com <http://www.mail.com/Product.aspx>!

------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=462&dsMessageId=1110352
Received on 2009-02-06 04:33:35 CET

This is an archived mail posted to the Subversion Dev mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.