From: Matthias Urlichs <smurf@smurf.noris.de>
Date: Thu, 02 Jun 2005 10:04:17 GMT
Subject: Re: [SCRIPT] cg-rpush & locking
Message-ID: <20050602100417.GG16616@kiste.smurf.noris.de>
In-Reply-To: <20050602073205.GA31482@muru.com>

Hi,

Tony Lindgren:
> I don't think locking for the duration of the push really is a problem.
> It is unlikely that there would be so many people pushing that it would
> cause inconvenience... Of course it would be nice to optimize it if
> possible.
> 
Since an 'atomic' cmpxchg operation is actually easier to program than a
lockfile with timeout handling etc., I would hope so. ;-)

> I would assume the biggest problem for most people is how they can push
> through a firewall. From that point of view it would make sense to do
> the push as a cgi script rather than something over ssh.

When in doubt, do both ... I'd certainly prefer ssh if at all possible.

> And with a cgi script you can of course optimize the locking and use
> tmp files before renaming which are a bit hard to do with rsync.
> 
rsync is going away anyway for git usage (long-term), I'd assume. It
certainly becomes more and more ineffective the more our history is
growing.

-- 
Matthias Urlichs   |   {M:U} IT Design @ m-u-it.de   |  smurf@smurf.noris.de
Disclaimer: The quote was selected randomly. Really. | http://smurf.noris.de
 - -
No one can guarantee the actions of another.
		-- Spock, "Day of the Dove", stardate unknown