Paolo Ardoino

What about creating a repo pigato-discovery and use something like this https://github.com/agnat/node_mdns ? I think it shouldn't be integrate in the main repo. Then pigato-discovery could offer more discovery options...

This is nice https://github.com/wankdanker/node-discover

It's sounds a good starting point. For the plain method, shouldn't we pass an object with credentials in the client and worker? For the broker having a callback to authenticate...

@leonpegg Not actually a coding style guide. I should write down something. Could you call "authHandler" instead of "zapHandler" and use the flag "auth" instead of "zap"? Anyway let's start...

This is still happening on x1 carbon gen 9, using 4.14.1-4

Thank you. @bmeck what do you think?

@bmeck Yes. Titanic could be the solution for persistent requests. For encryption and authentication I think we should try to integrate libcurve https://github.com/zeromq/libcurve and zap But I would also add...

pigato is here :) https://github.com/prdn/pigato I have refactored examples and a bit of documentation the help new developers to use the platform. I'm going to publish also some real-world examples.

It shouldn't be difficult to change from eventemitter to streams. Basically there are two main methods : send and flush Changing these methods to act with streams shouldn't be difficult......

It is a 'dealer' socket and it is defined as follows: ``` this.socket = zmq.socket('dealer'); this.socket.identity = new Buffer(this.name); this.socket.setsockopt('linger', 0); ``` To reproduce try this issue you could test...