On Oct 23, 2007, at 11:38 AM, Karl Fogel wrote:
>> Karl had some suggestions about a couple of different ways to fix it.
>>
>> Is this something that would be "easy" to do?
>
> ...
> An alternative (for less load on the slave) is for the client to
> notice the particular error from the slave, and contact the master
> itself. But that might have working copy metadata implications.
Or even network topology challenges. It would be easy to set up a
configuration where the clients are firewalled away from the master,
can only speak to the slave (and only the slave can speak to the
master). I'm not sure I believe it would be a good idea: basically
you're putting your server into the network DMZ, but your server's
the data you want best guarded, not least! But just 'cause I don't
think it's a useful idea does not mean some crazy IT manager won't do
it. Indeed, simply because it's called a "Proxy" might make this
more likely, as that word is also widely used for "the computer in
the DMZ that the clients talk to in order to get to the Internet."
-==-
Jack Repenning
Chief Technology Officer
CollabNet, Inc.
8000 Marina Boulevard, Suite 600
Brisbane, California 94005
office: +1 650.228.2562
mobile: +1 408.835.8090
raindance: +1 877.326.2337, x844.7461
aim: jackrepenning
skype: jrepenning
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Tue Oct 23 08:25:31 2007