yosh

@rekshark ehh, by socket I mean REQ socket on the API side; like with http. That's the way to approach it? :)

@yoshuawuyts well, too much latency for waiting on a new socket, so I might try to reuse a set of sockets if possible

@rekshark :( but that means I need to implement socket pooling of some sorts; that seems non-trivial - was hoping nanomsg would handle this

@yoshuawuyts ya filtering on a uuid might be easier, but you could pop sockets between active/available arrays

@rekshark looks like on the handler side things aren't any better: RES appear to be capped at 1 connection :( http://www.freelists.org/post/nanomsg/REQREP-worker-example,12 …

@yoshuawuyts that's right, hey this sounds like a use case for nn_device!

@rekshark oooh, yeah it's built for multiplexing connections right? It's the part I've still touched least, how'd I position it? :D

@yoshuawuyts try AF_SP_RAW family when creating nn_device, and you may need sudo privlges. AF_SP_RAW+REQ == Router; AF_SP_RAW+REP == Dealer