On 12/17/2006 6:45 PM, Wesley J. Landaker wrote:
> On Sunday 17 December 2006 15:03, Bob Smith wrote:
>> Thanks for the suggestion.
>> If I understand you correctly, given a URL of (say) svn.example2.com,
>> the SVN client would query the DNS SRV record for that domain to
>> obtain a port # (say, 3691) and target domain (say, example.net), then
>> send the svn request to example.net on port 3691, at which point the
>> svnserve on example.net would process the request.
> That's correct.
>> In order for this to work, wouldn't a single svnserve have to listen
>> on multiple ports and have different roots associated with each? That
>> sounds like a good idea, but my cursory reading of svnserve/main.c
>> suggests that it doesn't do that currently, so perhaps I've
>> misunderstood, or perhaps this is just more of what needs to change in
>> order to implement your idea.
> The easiest way to implement this would would be to run svnserve with
> different paremeters (i.e. for setting the root) on each of the different
> ports. svnserve itself wouldn't need to be modified or know handle more
> than one root. (And, for example, if you used inetd, there wouldn't really
> any additional static process overhead).
OK, for some reason I got it in my craw that running more than one
copy of the server would be suboptimal. I'm running Red Hat Linux
Bob Smith - bsmith_at_sudleyplace.com - http://www.sudleyplace.com
Received on Mon Dec 18 03:18:21 2006