4 ms·
Two things: 1) If you need a central name directory to point to the locations of various services, we already have DNS and DNS-SD. 2) I've been investigating
by zacharyvoase 14y ago
Two things:
1) If you need a central name directory to point to the locations of various services, we already have DNS and DNS-SD.
2) I've been investigating mDNS+DNS-SD (a.k.a. Bonjour, a.k.a. Avahi) as a potential solution. One can advertise ØMQ sockets at the host and link-local level, potentially with forwarding between subnets if you're inclined to configure it that way.
However, be warned that you shouldn't expose ØMQ sockets over non-trusted networks. It's still possible to induce bad errors (including aborts and segfaults) by sending malformed data to an open ØMQ socket.
- rumcajz 14y agoWe've implemented a DNS-based transport for ZeroMQ, but I am not quite sure it can be made work especially in WAN environment. DNS propagation delay can take several days which is not always an option for application names (as opposed to hostnames). As for the aborts, I've put all of them there myself, no need to remind me :)
- zacharyvoase 14y agoYou don't need DNS to propagate across the WAN. Just set up your own root server. You'll have low-enough load to set near-zero TTLs (or just have a single root server which everything uses). Although I admit I don't know enough about your use-case.