On 7/27/2010 6:09 AM, Matt Weinstein wrote: > Since C++ developers are used to reading from an istream and writing > to an ostream, the suggestion makes a lot of sense. >
And ... stdin. stdout used across a whole slew of the languages supported by ZMQ. These are invariably unidirectional, so I think it works pretty well. 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 => zmq::pipeline::outstream, zmq::pipeline::instream, zmq::multicast::publisher, zmq::multicast::subscriber zmq.pipeline.outstream, zmq.pipeline.instream, etc... **Again** Consider these training wheels. Stuff that reads well for folks trying to leverage ZeroMQ for their transition from serial-programming to parallel, who are likely to run away screaming when they can't figure out who's upstream and who's down :) - Oliver _______________________________________________ zeromq-dev mailing list [email protected] http://lists.zeromq.org/mailman/listinfo/zeromq-dev
