-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Martin Langhoff wrote: > The short of it is that mdns/dns-sd make sense for a small, > underutilised network of peers. They assume that the network is a > cheap resource, that broadcast messages are cheap, and that there is > no coordinating server.
mDNS assumes all of the above things. DNS-SD does not. DNS-SD is perfectly happy to work on a standard DNS server. From the spec """ This document proposes no change to the structure of DNS messages, and no new operation codes, response codes, resource record types, or any other new DNS protocol values. This document simply specifies a convention for how existing resource record types can be named and structured to facilitate service discovery. """ (http://files.dns-sd.org/draft-cheshire-dnsext-dns-sd.txt) I'm not particularly knowledgeable about the XS service discovery requirements, nor about DNS, so I can't reasonably tell you to use DNS-SD. What I can say is that it seems like it should be workable. - --Ben -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.10 (GNU/Linux) iEYEARECAAYFAknsW+UACgkQUJT6e6HFtqSx5QCglzpN+96F9aTAH05KnsQszg3E vy4An0lCtq/z04OKiFVvv5TvXUcNnkZ5 =TRBq -----END PGP SIGNATURE----- _______________________________________________ Server-devel mailing list Server-devel@lists.laptop.org http://lists.laptop.org/listinfo/server-devel