You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hello,
With the current API pullers pull without limit, I mean you can't control the pull process, the data is just accepted and flows in. Without this control is very hard to implement distributed workers, I have to use req rep.
I've hit the same problem with the zeromq node bindings. It will be great if one can pause and resume the pull process (like readable streams) or at least call socket.pull(function (msg) {}) or something like that.
I think pullers should pull messages whenever they need or I'm missing something obvious?
The text was updated successfully, but these errors were encountered:
Hello,
With the current API pullers pull without limit, I mean you can't control the pull process, the data is just accepted and flows in. Without this control is very hard to implement distributed workers, I have to use req rep.
I've hit the same problem with the zeromq node bindings. It will be great if one can pause and resume the pull process (like readable streams) or at least call
socket.pull(function (msg) {})
or something like that.I think pullers should pull messages whenever they need or I'm missing something obvious?
The text was updated successfully, but these errors were encountered: