[zeromq-dev] ZeroMQ REQ/REP on ipc:// and concurrency

[Pieter Hintjens]

Please read the Guide, work through the examples, and when you have
questions, frame them with test code we can look at.

Thanks
Pieter

On Thu, Jun 7, 2012 at 7:35 AM, Matteo Fortini <matteo.fortini at gmail.com> wrote:
> [ I asked this question on stackoverflow, too, if you
> prefer: http://stackoverflow.com/q/10918276/107969?sem=2 ]
>
> I implemented a JSON-RPC server using a REQ/REP 0MQ ipc:// socket and I'm
> experiencing strange behavior which I suspect is due to the fact that the
> ipc:// underlying unix socket is not a real socket, but rather a single
> pipe.
>
> From the documentation, one has to enforce strict zmq_send()/zmq_recv()
> alternation, otherwise the out-of-order zmq_send() will return an error.
>
> However, I expected the enforcement to be per-client, not per-socket. Of
> course with a Unix socket there is just one pipeline from multiple clients
> to the server, so the server won't know who it is talking with. Two clients
> could zmq_send() simultaneously and the server would see this as an
> alternation violation.
>
> What about tcp:// sockets? Will it work concurrently? Should I use some
> other locking mechanism to work around this?
>
> Thank you,
> Matteo
>
> _______________________________________________
> zeromq-dev mailing list
> zeromq-dev at lists.zeromq.org
> http://lists.zeromq.org/mailman/listinfo/zeromq-dev
>