On Tue, Jul 27, 2010 at 3:16 PM, Oliver Smith <[email protected]> wrote:
> I would kind of like to see the pattern name be incorporated, but that > would perhaps be addressed later as a "formal socket names" type thing, > something that could be done in a namespace friendly fashion, e.g. > ZMQ_PIPELINE_OUTSTREAM, ZMQ_PIPELINE_INSTREAM, ZMQ_PUB, ZMQ_SUB If you're going to incorporate the pattern names, I'd suggest using abbreviations, and doing it consistently for all socket types. And there are no streams afaic :-) So: ZMQ_PIPE_OUT, ZMQ_PIPE_IN, ZMQ_PUBSUB_OUT, ZMQ_PUBSUB_IN and maybe ZMQ_REQREP_CLIENT and ZMQ_REQREP_SERVER ZMQ_REQREP_CLIENT_ASYNC and ZMQ_REQREP_SERVER_ASYNC ZMQ_PEER_NODE /me continues to plead for consistency. -Pieter _______________________________________________ zeromq-dev mailing list [email protected] http://lists.zeromq.org/mailman/listinfo/zeromq-dev
