[zeromq-dev] 0MQ + standard RPC

Matthew Long matthew.long at aptomar.com
Mon Nov 28 12:26:12 CET 2011


I'll take a look at doing that.  I'm a little cautious about this since the documentation strongly hints that we shouldn't play around with the raw file descriptor too much, but maybe with the right wrapper this wouldn't be too bad.

For Go, in particular, I'd like to use the standard RPC mechanism.  With multipart messages and a simple definition of an RPC header and body, the code to pack and unpack messages is ridiculously simple using XREP and XREQ.  It is just the handling of the polling of what needs to be sent and received that is messy -- and my solution for handling that started to look awfully like a variant of some of the standard libraries.  



On Nov 28, 2011, at 11:56 AM, Ian Barber wrote:

> On Mon, Nov 28, 2011 at 10:45 AM, Matthew Long <matthew.long at aptomar.com> wrote:
> Hi Martin,
> We will heavily leverage the 0MQ PUB/SUB functionality in most of the communication layer that we are building.  The RPC portion is just one piece of what we are doing -- in general it is simply going to be the control channel.
> If 0MQ is not a good fit for this piece, it is not a big deal, but I had hoped that some of what you have built into 0MQ (such as durable sockets) could help simplify some of the application layer.
> Matt
> Not sure if it helps, but if any of your RPC code can operate on a file descriptor, you can get that for the ZMQ socket, and use that to poll and so on. 
> Ian
> _______________________________________________
> zeromq-dev mailing list
> zeromq-dev at lists.zeromq.org
> http://lists.zeromq.org/mailman/listinfo/zeromq-dev

More information about the zeromq-dev mailing list