On 7/27/2010 11:01 AM, Pieter Hintjens wrote: >> Primarily: using stdin/stdout may cause naming conflicts and confusion >> > Probably. The pipeline pattern is the only one without clear roles > for nodes (see http://api.zeromq.org/zmq_socket.html) >> 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. >> > Borrowing is good, especially when it works as you'd expect. > Yep - but in this case I think there is too much baggage with borrowing the 'std' prefix there :) Just the suffix (in/out) should be sufficient, because it follows the paradigm ... stdin, stdout, STDIN, STDOUT, std::cin, std::cout, etc, etc.
> I'd be careful about inventing new concepts (generator, broker) that Valid point, consider broker/generator withdrawn :) >> ZMQ_SOCK_BROADCAST_PUBLISHER (aka ZMQ_PUB) => zmq.sock.broadcast.publisher >> ZMQ_SOCK_BROADCAST_SUBSCRIBER (aka ZMQ_SUB) => zmq.sock.broadcast.subscriber >> > BROADCAST is nice but the pattern is called "pubsub" and one reason > for the long names is to make pattern names explicit so people are > less likely to mix the wrong socket types. If we were going to rename > it, I'd suggest TOPIC, which is an existing unsurprising term. > I think PUBSUB works well enough. - Oliver _______________________________________________ zeromq-dev mailing list [email protected] http://lists.zeromq.org/mailman/listinfo/zeromq-dev
