13.04.2011, 09:10, "Martin Sustrik" <[email protected]>: > > Most people want some kind of "route to address" mechanism so that they > can send messages to specific instances of services. Once you start > working on a solution for that problem you'll find out that you are > basically duplicating the IP's routing functionality, distribution of > routing tables etc. So the question at the moment is: What exactly > should 0MQ provide in this scenario that is not already covered by IP? > When we have the answer, it will be much easier to think about the solution.
Yes, you can say that this is covered by IP. But isn't what covered by IP is also covered by ethernet? What we want is logical addresses at zeromq level, which means both the possibility that two services would be on same machine, and the posibility that two machines will be used as a single logical node. Same happens with the network at every level: we theoretically could leave with single site per ip and give a machine several IP adresses, but usually we use domain names to both: group sites on single IP and load-balance single site to different IPs. -- Paul _______________________________________________ zeromq-dev mailing list [email protected] http://lists.zeromq.org/mailman/listinfo/zeromq-dev
