Hi Kahn-Chan, It's a feature - inproc transport doesn't supported unordered bind or connect. A map of endpoints are maintained per context - you'll get that error if and when there's no "bound" address when trying to connect.
- Lourens On Thu, Oct 18, 2012 at 5:55 PM, Kah-Chan Low <[email protected]> wrote: > Hi, > When I do this I will get a "connection refused" error: > > socket1.connect("inproc://abc"); > socket2.bind("inproc://abc"); > > When I reverse the order of the statements everything works fine. > Both sockets have been created with the same ZMQ context. > > Is this a feature or a bug? > > Thanks! > KC > > > > _______________________________________________ > 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
