inproc support is special in zmq: in particular it completely bypasses the auth layer, which causes problems in OxenMQ because we assume that a message will always have auth information (set during initial connection handshake).
This adds an "always-on" inproc listener and adds a new connect_inproc method for a caller to establish a connection to it.
It also throws exceptions if you try to listen_plain or listen_curve on an inproc address, because that won't work for the reasons detailed above.
inproc support is special in zmq: in particular it completely bypasses the auth layer, which causes problems in OxenMQ because we assume that a message will always have auth information (set during initial connection handshake).
This adds an "always-on" inproc listener and adds a new
connect_inprocmethod for a caller to establish a connection to it.It also throws exceptions if you try to
listen_plainorlisten_curveon an inproc address, because that won't work for the reasons detailed above.