it is not synchronous versus asynchronous.
it is somehow deeper than that, but confused because in one
small part of the space, they overlap.

i will take a stab out some text, post it here for comments, then pieter
can think about if, or how, he might add it to the guide.

        andrew

On Jun 25, 2011, at 12:37 AM, Martin Sustrik wrote:

> On 06/25/2011 02:41 AM, Andrew Hume wrote:
> 
>> i think this meme is quite common; nearly all instances of complaints
>> about 0mq's
>> scheduling and buffering, slow joiners and the like, are examples of
>> this -- we want 0mq
>> to trivially do job scheduling for us as well as all the other stuff.
> 
> That's a good point! If should definitely be stressed out. The text 
> would have to explain the difference between the two though which is not 
> a trivial task. Or would a statement that job scheduling is inherently 
> synchronous while network routing is inherently asynchronous do?
> 
> Martin
> _______________________________________________
> zeromq-dev mailing list
> [email protected]
> http://lists.zeromq.org/mailman/listinfo/zeromq-dev


------------------
Andrew Hume  (best -> Telework) +1 623-551-2845
[email protected]  (Work) +1 973-236-2014
AT&T Labs - Research; member of USENIX and LOPSA




_______________________________________________
zeromq-dev mailing list
[email protected]
http://lists.zeromq.org/mailman/listinfo/zeromq-dev

Reply via email to