Re: Implement SRV DNS

> > > there's already some SRV code in the GNOME CVS.
> For what?

This is part of Zeroconf integration, if I understood correctly:

http://lists.gnome.org/archives/desktop-devel-list/2004-March/msg00458.html

> SRV's primary usefulness is replicating a service among multiple
> servers.

It's only one of the main goals of SRV records.

> You can replicate an SVN server for read-only access, but it's kind of
> hackish and I doubt many people do it.

You can at least use hooks to re-commit everything you do in a
repository in another one. Then, if the first SVN fall down, the second
can be used as fallback. When the master is up again, it just has to
refuse connections as long as it is not synced back.

<disclaimer>

I don't want to start a flaming discussion about replication. Let's say
it remains a possible use of SRV RR with SVN.

</disclaimer>

> SRV is also useful for redirecting a service to a different domain (in
> the same way that MX allows you to have mail service and web service
> at the same domain without running an SMTP and HTTP server on the same
> machine), but that's kind of a marginal justification; people just
> aren't going to mind advertising svn://svn.foo.bar/ instead of
> svn://foo.bar/ for version control access.

But this feature of SRV has one another very interesting use: you don't
have to know where lives the SVN server (host AND port), and the
administrator can arbitrarily move it without telling anyone he's doing
this. If he modifies the SRV records, everyone will contact the new
server when it's moved...

It also provide a mean to host many SVN server, at different ports.So
svn://foo.bar/ can lead to dedicatedhost.bigcompany.com:12345, and
svn://bigcompany.com/ to dedicatedhost.bigcompany.com:3690...

So SRV records DO provide interesting features for Subversion, IMHO.

Quickly,
le Moine Fou

-- 
pierre.thierry@moine-fou.org
OpenPGP 0xD9D50D8A