| |||||||||||||
0MQ: A new approach to messaging0MQ: A new approach to messagingPosted Jan 22, 2010 7:27 UTC (Fri) by sustrik (guest, #62161)In reply to: 0MQ: A new approach to messaging by ortalo Parent article: 0MQ: A new approach to messaging
That's pretty interesting question. We've done a lot of experimenting about how to provide location transparency (using symbolic rather than physical addresses in bind & connect).
At the moment the idea is that symbolic name resolving can be offloaded to the DNS. Also recall that domain name resolving (at least on Linux) doesn't mean DNS alone. You can hook into it quite easily. You can even plug in an LDAP server, so you can define your endpoints in a directory service. Anyway, the whole topic needs more thinking and design work.
(Log in to post comments)
0MQ: A new approach to messaging Posted Jan 22, 2010 15:42 UTC (Fri) by mato (subscriber, #964) [Link]
Using DNS for locating 0mq services would be very cool. Martin, I don't know if you're aware but DNS can store many record types, so we could invent a format for 0mq service records and then implement something like dns://service.example.com for lookup which would grab the appropriate record and decode that into a proper transport://endpoint.
Something to discuss on the dev list...
0MQ: A new approach to messaging Posted Jan 22, 2010 18:31 UTC (Fri) by sustrik (guest, #62161) [Link]
Sound just too cool to be true :) Let's move this discussion to the mailing list.
0MQ: A new approach to messaging Posted Jan 22, 2010 18:32 UTC (Fri) by dlang (✭ supporter ✭, #313) [Link]
why not use one of the existing resource/service record definitions?
|
|||||||||||||