[zeromq-dev] [PATCH] Introduce ZMQ_ROUTER and ZMQ_DEALER sockets

Pieter Hintjens ph at imatix.com
Mon Jun 20 14:31:40 CEST 2011

2011/6/20 Fabien Niñoles <fabien.ninoles at gmail.com>:

> Could you develop a little more on the new schemed identities ?  Would
> it be used only for back stack addressing or for all transient
> identities ?

My idea is to use them for ROUTER, and also make them available for
other socket types via a getsockopt.

With respect to address reuse, ROUTER in any case needs to inform the
application about connection shutdown, so that applications can
properly clean up any state.

With respect to security, that has to be handled at a different level
in any case afaics.

> How would they be distinguished from permanent
> identities ?

Permanent identities would either not be allowed, or also have to be schemed.

> Right now, all usage of such identity, apart from debugging/monitoring
> purpose, seems flawed to me.  Considering an IP with a transient port
> to be a safe identity is unsecure at best, and any scheme based on
> such data would not be able to scale correctly.

Please explain why it wouldn't scale?

> I would be very interested to see a real use case for such identity.

My reasons for exploring this aren't to turn the schemed identity into
a first-class concept, but rather to:

* use a natural key instead of a generated UUID
* provide a string value instead of a binary value (easier for
debugging and logging)

Some people may end up using the IP address for routing or message
filtering, and it's worth exploring, but that's not my goal.


More information about the zeromq-dev mailing list