It is not explicitly on the roadmap because most of the work on ZeroMQ is driven by contributions.
In my experience you can make inproc work very well by doing the bind and connect in one thread and then sending the socket to the other thread. It works in 2.1 because sockets can be moved between threads. In cases where you use threads to simulate processes, just use ipc, and it works like tcp. -Pieter On Sun, Jan 30, 2011 at 10:23 PM, Nathan Marz <[email protected]> wrote: > I saw in the guide that unlike the other transports, inproc requires the > bind to happen before the connect. In the system I'm building, this is very > inconvenient and I'm probably going to just use ipc transports to avoid the > complexity of getting the various pieces to synchronize correctly. I didn't > see anything about this issue on the "0mq 3.0 Roadmap" -- is there any > timeline on when this will be fixed? > > Thanks, > Nathan > -- > Twitter: @nathanmarz > http://nathanmarz.com > > > _______________________________________________ > zeromq-dev mailing list > [email protected] > http://lists.zeromq.org/mailman/listinfo/zeromq-dev > > _______________________________________________ zeromq-dev mailing list [email protected] http://lists.zeromq.org/mailman/listinfo/zeromq-dev
