Comments for page "Location-independent Addressing with Messaging Middleware"

(no title)

Thu, 09 Jan 2014 23:41:24 +0000

Hi,

After working a bit more with message systems I would like to bring up the ROUTER functionality again. I totally agree still with DSN or SRV record solutions, but also like the idea of having a topology where I can send a message to a address which is not directly resolvable by DNS but routed by a given ROUTER which feels responsible. a pure DNS to IP mapping for for MyApplication name would be enough here? I would like to send a message to myApplication even if it not direct reachable by a TCP connection as it routed by a edge DEVICE, ROUTER etc.

(no title)

Sun, 06 Jan 2013 18:48:17 +0000

The main point of the article is that the location-independent addressing is no business for messaging. It should be done on other layer(s) of the stack.

As for the exact mechanism to use, I am in no way expert in the area. AFAIK there are mutliple attempts for solution, but none of them is widely accepted (to the point where you can just do connect (s, "myApplication") and the stack will do the rest for you).

Not being an expert means that I can only guess what are the reasons behind functionality so fundamental not being ubiquitous. Anyway, my guess would be that the problem is the inherent tension between requirements for LANs (dynamic discovery of services) and requirements for WANs (statically configured service names, such as DNS SRV records).

(no title)

Sat, 05 Jan 2013 10:03:26 +0000

I strongly agree with DNS name resolution here, but what you describe sounds so familiar with running DIAMTER over SCTP. Where SCTP gives you some form of message absctraction and DIAMTER Base Protocol can (it is not mandatory) resolve the endpoints by asking for SRV/NAPTR records described in RFC 3588 and updated recently here:
RFC 6733 section 5.2 (sorry cant post a link here)

(no title)

Mon, 17 Dec 2012 20:13:55 +0000

SRV records are step in the right direction. However, there's much more to it. On LAN, for example, you want the services to be registered and discovered dynamically, rather than inserted by hand into DNS (think DNS-SD) Also, I guess, some kind of scoping is needed (local service with same name shadows the global service) Etc.

Once the following works out of the box on LAN, we're pretty close:

 s1 = socket (AF_INET, SOCK_STREAM, 0); bind (s1, "myApplication1"); ... s2 = socket (AF_INET, SOCK_STREAM, 0); connect (s2, "myApplication1");

(no title)

Mon, 17 Dec 2012 15:52:55 +0000

"And once again, the solution is pretty straightforward. We need a directory service to map application names to IP addresses."

Isn't what you're describing the same as DNS SRV records? It sure seems like it:
hxxp:// en.wikipedia.org /wiki/ SRV_record