Pieter's list:
http://www.zeromq.org/draft:socket-type-names
* ZMQ_SOCK_REQREP_CLIENT (aka ZMQ_REQ).
* ZMQ_SOCK_REQREP_SERVICE (aka ZMQ_REP).
* ZMQ_SOCK_REQREP_CLIENT_ASYNC (aka ZMQ_XREQ).
* ZMQ_SOCK_REQREP_SERVICE_ASYNC (aka ZMQ_XREP).
* ZMQ_SOCK_PUBSUB_PUBLISHER (aka ZMQ_PUB).
* ZMQ_SOCK_PUBSUB_SUBSCRIBER (aka ZMQ_SUB).
* ZMQ_SOCK_PIPELINE_STDIN (aka ZMQ_PIN).
* ZMQ_SOCK_PIPELINE_STDOUT (aka ZMQ_POUT).
* ZMQ_SOCK_EXCLUSIVE_PEER (aka ZMQ_PAIR).
My $0.01 (I'm too cheap to go the whole $0.02 just yet ;)
Primarily: using stdin/stdout may cause naming conflicts and confusion
-- they are only borrowing from the concept of stdin/stdout, they are in
no way related. Plus we don't want someone to misunderstand them as the
default sockets for zmq.
ZMQ_SOCK_REQREP_GENERATOR (aka ZMQ_REQ, the requester) =>
zmq.sock.reqrep.generator
ZMQ_SOCK_REQREP_BROKER (alias for ZMQ_REP, the responder) =>
zmq.sock.reqrep.broker
ZMQ_SOCK_REQREP_GENERATOR_ASYNC (aka ZMQ_XREQ) => problem
ZMQ_SOCK_REQREP_BROKER_ASYNC (aka ZMQ_XREP) => problem
ZMQ_SOCK_BROADCAST_PUBLISHER (aka ZMQ_PUB) => zmq.sock.broadcast.publisher
ZMQ_SOCK_BROADCAST_SUBSCRIBER (aka ZMQ_SUB) => zmq.sock.broadcast.subscriber
ZMQ_SOCK_PIPELINE_OUT (aka ZMQ_POUT) => zmq.sock.pipeline.out
ZMQ_SOCK_PIPELINE_IN (aka ZMQ_PIN) => zmq.sock.pipeline.in
ZMQ_SOCK_EXCLUSIVE_PEER (aka ZMQ_PAIR) => zmq.sock.exclusive.peer
- Oliver
_______________________________________________
zeromq-dev mailing list
[email protected]
http://lists.zeromq.org/mailman/listinfo/zeromq-dev
