[zeromq-dev] 0MQ + standard RPC

[Burak Arslan]

hiya,

fwiw, i've built a simple rpc system on zeromq using the req/rep pattern.

https://github.com/arskom/rpclib/blob/master/src/rpclib/server/zeromq.py
https://github.com/arskom/rpclib/blob/master/src/rpclib/client/zeromq.py

best,
burak

On 11/28/11 11:55, Matthew Long wrote:
> Hi all,
>
> I have been experimenting quite a bit with 0MQ over the past few weeks and have been designing various forms of data transport for some of our applications.  All is well and good there.
>
> But one key piece that we need to build (in a cross-platform / cross-development-environment manner) is an RPC layer.  Initially we are targeting C++ and Go environments.   So far I have been looking at the gozmq package for Go and a colleague is using the standard bindings for C++.  One other constraint is that we are using protocol buffers for serialization.  We can get 0MQ running with both, but the RPC implementation is a bit wonky and ad-hoc in my view, so I wanted some advice from the list.
>
> Ideally I would like to be able to integrate 0MQ as a transport layer, but use the rest of the RPC stack (in a way that fits the language).  The RPC layers we are looking at  already have all of the reflection, method invocation, timeout, polling, etc that the application level needs.   As it stands now, it seems like I am re-implementing a good chunk of existing code just to fit 0MQ.  What would help is a 0MQ messaging pattern that simply says "emulate a standard TCP socket".
>
> Has anyone built a shim layer or something similar that does something similar?
>
> The big tradeoff seems to be:
> 1)  whether I want to do the work to fit 0MQ into a working RPC layer or;
> 2) build an RPC layer on top of 0MQ and rewrite most of the RPC stack.
>
> Does anyone have any suggestions here?
>
> Thanks,
>
> Matt
> _______________________________________________
> zeromq-dev mailing list
> zeromq-dev at lists.zeromq.org
> http://lists.zeromq.org/mailman/listinfo/zeromq-dev