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.
> 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).
Wesley J. Landaker <firstname.lastname@example.org> <xmpp:email@example.com>
OpenPGP FP: 4135 2A3B 4726 ACC5 9094 0097 F0A9 8A4C 4CD6 E3D2
Received on Mon Dec 18 00:44:47 2006
- application/pgp-signature attachment: stored