[cvsnt] Re: Distributing load across several CVSservers(Transparent Proxy)

[Lahav Savir]

Currently I'm using CVSYNC to have a local mirror of my remote
repository,
This works great and it seems extremely efficient (running it every 10
minutes) so my developers gets changes almost in real-time.

The only missing part is to allow uses to check in locally (via
transparent proxy, or redirection).

I'll be please to run some test as soon as this becomes available

Lahav

-----Original Message-----
From: Paul Kramer [mailto:kramicus at yahoo.com] 
Sent: Sunday, December 12, 2004 7:38 PM
To: cvsnt at cvsnt.org
Subject: RE: [cvsnt] Re: Distributing load across several
CVSservers(Transparent Proxy)


Hello,
 
I've thought about, but not prototyped the idea of accomplishing
remote/distributed development with CVS by cloning the master repository
for each of the remote sites, and then sync by way of vendor branches.
Any thoughts about that?
 
Paul

Lahav Savir <LahavS at ixi.com> wrote:
The main issue is that check-outs / updates are much faster 
especially when you have many developers working on the same repository.

So in that case commits take little longer, but you can commit them to
the local server and not change the CVSROOT for committing to Master
server.

Lahav



-----Original Message-----
From: Tony Hoyle [mailto:tmh at nodomain.org] 
Sent: Sunday, December 12, 2004 1:15 PM
To: cvsnt at cvsnt.org
Subject: [cvsnt] Re: Distributing load across several CVS
servers(Transparent Proxy)


Raymond Zhang wrote:
> As this is a very useful feature for distributed development teams
> working on the same project in different countries, esp. those with 
> very poor network infrastructure. I am wondering whether CVSNT also 
> have or planning to have such features?

What it does it not distributed development, but proxying. You still 
need a live connection to the remote server via the proxy, so in the 
instance of poor network infrastructure there is no gain (In practice I 
suspect there's little gain in the case of a good network infrastructure

either, since almost everything requires a live link to the repository -

you can't really proxy very much).

> I love CVSNT for its integrated authentication with Windows and easy
> management of access control through windows file system. But this 
> transparent proxy feature is just a feature that is too important to 
> miss.

It's relatively easy to write but all it gives you is the ability to use

the same server in your root files rather than specifying different
ones.

True distributed development is much harder and will be in a future 
cvsnt release at some point.

Tony
_______________________________________________
cvsnt mailing list
cvsnt at cvsnt.org http://www.cvsnt.org/cgi-bin/mailman/listinfo/cvsnt
_______________________________________________
cvsnt mailing list
cvsnt at cvsnt.org http://www.cvsnt.org/cgi-bin/mailman/listinfo/cvsnt
_______________________________________________
cvsnt mailing list
cvsnt at cvsnt.org http://www.cvsnt.org/cgi-bin/mailman/listinfo/cvsnt