Zeroconf solves two issues at the same time through mdns: IP without DHCP and names without DNS.
The part related to service registration/discovery (names) is not trivial but not that hard to mimic, especially if we follow the detailed 60 pages on the subject in "Zero Configuration Networking" (O'Reilly). They describe precisely how they avoid name clash and ARP floods. The idea behind starting zconf is to experiment and see if we can have something easier to work with then avahi/zeroconf/LLMNR. Gaspard PS: Christian, if you want to join forces, give me your github login. On Tue, Sep 14, 2010 at 3:03 PM, Christian Gudrian <[email protected]>wrote: > Am 14.09.2010 14:42, schrieb Kelly Brock: > > > Zeroconf is actually a relatively tricky protocol > > I'm not trying to implement _the_ Zeroconf protocol (as did avahi and > Bonjour). I was thinking of a much simpler approach that does not > require a locator service. Let's say a client needs a certain service. > During startup the client multicasts a request for that service and > receives responses of all running service instances. Any new service > likewise multicasts a message during startup so that all clients can > update their local service list. > > Christian > _______________________________________________ > zeromq-dev mailing list > [email protected] > http://lists.zeromq.org/mailman/listinfo/zeromq-dev >
_______________________________________________ zeromq-dev mailing list [email protected] http://lists.zeromq.org/mailman/listinfo/zeromq-dev
