News for hackers. Stuff that matters.
Re:Location-independent Addressing with Messaging Middleware by zacharyvoase on Sunday December 16, 2012 @04:41PM (#4929657)
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.

Re:Location-independent Addressing with Messaging Middleware by rumcajz on Sunday December 16, 2012 @04:49PM (#4929691)
We'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 :)

Re:Location-independent Addressing with Messaging Middleware by zacharyvoase on Thursday December 20, 2012 @06:02AM (#4947076)
You 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.