2011/11/11 Ilja Golshtein <[email protected]>:
> Hello.
>
> I am sorry to ask, but is this type check really useful?
>
> Assuming the goal is to make 0mq more user friendly and to reduce chances of
> erroneous setup,
> I suggest we should introduce socket names (identities is much better word,
> but
> is it already in use) and check this names are matched.
>
> Type match is too weak even for sanity check and it could be implemented only
> because
> it is not too difficult ...
I'd second this proposal, as I've described in SP mailing list. There
is slight difference in proposed semantics. I'd like to have single
"topology_id" which is shared between endpoints and devices. So type
check is also useful to decide is it right place to connect (e.g. it's
input or output port in a device).
The problem is that's it's another step to configure at each socket.
But it can be a plus for migration, like:
s1, s2 = zmq.socket(zmq.REQ), zmq.socket(zmq.REQ)
s1.setsockopt(zmq.TOPOLOGY_ID, "dummy_service")
s1.connect("ipc://dummy1") # speaks new protocol, providing type checks
s2.connect("ipc://dummy2") # speaks old protocol
--
Paul
_______________________________________________
zeromq-dev mailing list
[email protected]
http://lists.zeromq.org/mailman/listinfo/zeromq-dev
