To add on to that, here are the few things to consider when writing the zmq binding:
1. REQ/REP should be a lockstep: REQ -> REP -> REQ -> REP. The binding's exported API should reflect this. 2. The rest (PUSH/PULL/ROUTER/DEALER/PUB/SUB) are all however, perfectly usable if used like an event emitter/polling style 3. 0MQ's own API does not have different API calls for REQ/REP and the rest of the sockets, so *ideally* your API shouldn't have separate API call styles 4. #3 is difficult to achieve for #1 if you choose to use any of nodejs's "async" styles: callbacks/eventemitters 5. Hence, as a low-level binding, it would actually be more useful if it were a direct copy of the 0MQ binding, and THEN let the nodejs community build upon it to create async libraries on top of the binding itself -- -- Job Board: http://jobs.nodejs.org/ Posting guidelines: https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines You received this message because you are subscribed to the Google Groups "nodejs" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/nodejs?hl=en?hl=en --- You received this message because you are subscribed to the Google Groups "nodejs" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
