[zeromq-dev] [otish] "Why ZeroMQ"
andrew at research.att.com
Tue Jul 27 13:32:08 CEST 2010
while one should not be a slave to history,
there is long established use of
- naming with respect to the computational entity
- for things to be plugged together: input and output
for example, unix programs in a pipeline use stdin and stdout
and with relatively little surprise to newcomers.
the difficulty i see, and had when i started 0mq, is that rather
than naming inputs and outputs, 0mq is naming protocol patterns
(that is how nodes cooperate), and the naming conventions
for nodes and the connections are fairly specific to each pattern.
and for me, that missing piece of documentation was the critical
one to me; this is the document that lists several to many common
patterns of data flow, and for each pattern, identifies each type of
node in the pattern, the channels involved, and how each node
implements their channels in 0mq.
but then again, maybe i don't grok 0mq well enough.
i certainly haven't had any epiphanies like other folks.
it hadn't occurred to me that you could do multiple 0mq sockets
over a single TCP/IP socket. and the documentation doesn't
lead you in that direction.
On Jul 26, 2010, at 4:40 PM, Nicholas Piël wrote:
> On Jul 26, 2010, at 10:15 PM, Oliver Smith wrote:
>> Pieter Hintjens said the following on 7/26/2010 2:53 PM:
>>> :) I personally do not like the current socket names, they seem
>>> inconsistent. There was a blog post with suggestions for new
>>> names but
>>> consensus was... we learned these names, don't change them now.
>> *begs for aliases* the upstream/downstream in particular is confusing
>> because the up/down is subjective to perspective and personal use of
> What alias would you suggest?
> I personally think that the naming of upstream/downstream is
> perfect for this unidirectional pattern. I use the 'wild water' or
> 'waterfall' metaphor where you can send something downstream but it
> is impossible to send something upstream (unless your a Trout). If
> you want to receive something you can only receive stuff from the
> upstream. Maybe this helps?
> By the way, great demo! :)
> zeromq-dev mailing list
> zeromq-dev at lists.zeromq.org
Andrew Hume (best -> Telework) +1 732-886-1886
andrew at research.att.com (Work) +1 973-360-8651
AT&T Labs - Research; member of USENIX and LOPSA
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the zeromq-dev