Support for zeromq 3.0 about zeromq.node HOT 16 CLOSED

Patches welcome ;).

Next time I have time I'll look into how much effort this would require.

from zeromq.node.

+1 :)

from zeromq.node.

Looks like the Datasift guys have already patched zeromq.node to support 0mq 3.0. https://github.com/datasift/zeromq.node

from zeromq.node.

Ok I forked the Datasift repo and incorporated some changes made to zmq via TJ. Now you can install from npm by doing sudo npm install zmq-3.0.

from zeromq.node.

maybe @JustinTulloss could give a few of us commit access so we can keep things up to date, not sure how active this project is

from zeromq.node.

@visionmedia Agree. I don't like cluttering NPM with unnecessary forks.

from zeromq.node.

Just FYI, the forked DataSift repo was done for zmq 3.0 support and has been used in our production HTTP and Websocket streaming service for a few months now and we've had no issues so far. It was a quick fix because at the time we were moving up to tens of thousands of messages (multiple times the size of the Twitter firehose) a second and zmq 3.0 did proper server-end filtering (zmq 2.0 sent all messages and filtered at the client end) of topics which reduced our internal network traffic a lot. We've not used all the different socket types, only pull/push and pub/sub.

from zeromq.node.

@ollieparsley Yes and coincidentally we are using only push/pull and pub/sub too :) Needed pub side filtering and hence this fork. Thanks!

from zeromq.node.

I would also like to avoid forking unnecessarily, but as I'm sure you've noticed I haven't spent much time on this project lately. @visionmedia, @shripadk are you both interested in having commit access?

from zeromq.node.

Also @ollieparsley, is your fork backwards compatible?

from zeromq.node.

@JustinTulloss yup that would be great! Agreed with the forking

from zeromq.node.

@JustinTulloss Great :)

from zeromq.node.

Ok, you're both added.

from zeromq.node.

wicked thanks man

from zeromq.node.

awesome :)

from zeromq.node.

Closing this, as we're 3.0 compatible.

from zeromq.node.