Bent Cardan

well ya of course. @ronkorving +1. and if libzmq gave us a streaming type of interface let's start there.

@nacholibre glad you saw my point, but hold up, you're saying pull is broken and that you might have a solution: > I cannot implement pull on demand with the...

@ronkorving bear with me pls: what event does `pull` emit so fast in succession? while pulling emit, emit, emit it's just firing message events like the normal callback pattern? ```...

ahh, :palm_tree: therefore one of your ten `pull` sockets may absorb unfair results. gotcha. @nacholibre, @ronkorving, this isn't just a slow joiner syndrome? those divide and conquer docs say only...

> Maybe sock.send() should have second parameter callback with argument for successful sending? sure you could do that but it won't change the problem of handler buildup from `pull`'s async...

woah @nacholibre hold up, your comment previous to this located and began to describe the precise nature of a `pull` socket deficiency rearing up in the JavaScript layer. Moreover you...

does a `socketopt` already sort this thing out in `pull`?

would you be able to push a quick ex. to illustrate: > try to implement push pull pattern with non trivial number of messages and you'll understand everything I'm saying....

while those horrific attacks yesterday in Paris test my focus doing software, I can still give you a nice scenerio now where backpressure doesn't matter. #### no need to worry...

hey thanks for helping me through this issue, i've learned a lot @ronkorving and @nacholibre now i completely agree with you guys. `pull` is borked. if anyone wants to compare...