Yoan Arnaudov

Hey, this is interesting functionality, can you give me example use case in which this will be helpful?

@janmarthedal Thanks for the contribution, I'll test it and add it in the next release if everything works as expected.

Hello, thanks for your contribution, but I cannot merge this before I know for sure this is better than original version. How did you verified your code is faster? Can...

I agree, also in the [ configuration example](https://github.com/EasyCorp/easy-deploy-bundle/blob/master/doc/configuration.md#configuration-files) the path suggested is `app/config/deploy_prod.php`, but in reality when you run the deploy command in it says `There is no config file...

@reqshark you have a point, I agree with you, but the current node bindings doesn't follow the so called ABI. Pull sockets should pull on demand, that is the point...

Method with callback function will solve the problem, something like this: ``` sock.recv(function(message) { console.log('message received'); }); ``` If I have some time I'll try to implement it and see...

@reqshark I agree with you, implementing streams in the current API is not a good idea and maybe is not a good idea at all, we should fix the pulling...

I think pull socket should have `recv` method with callback and pushSockets should have easy to access `pendingMessages` property. ``` javascript pushSocket.send(message); if (pushSocket.pendingMessages >= 500) { console.log('slow pullers, should...

What do you mean by that? Hwm? If you are talking about high water mark option I can tell you about my past experience with it - it doesn't work....

I've made my repo, because in yours you should npm install in the package directory. https://github.com/nacholibre/nodezmq.push.pull.example/ try to limit received messages in the consumer.js and try to limit outgoing pending...