According to the reference pages: http://api.zeromq.org/4-2:zmq-socket
Summary of ZMQ_ROUTER characteristics Compatible peer sockets *ZMQ_DEALER*, *ZMQ_REQ*, *ZMQ_ROUTER* So I don't think the design you are looking at will work. Mark On Wed, Mar 27, 2019 at 8:50 AM Jake <[email protected]> wrote: > I currently have a system that has two public ports, facilitating: > > REQ <-- tcp --> ROUTER <-- proxy --> DEALER <-- inproc --> REP > > and > > SUB <-- tcp --> PUB (various internal sinks supplying events) > > Is it possible to use a single public port for both the REQ and SUB socket > connections that routes them based on connection type? Something like: > > > REQ --\ /--ROUTER--DEALER--REP > ROUTER > SUB --/ \--PUB > > So there is only one TCP port listening required, a common CURVE > configuration point, etc? > > -Jake > _______________________________________________ > zeromq-dev mailing list > [email protected] > https://lists.zeromq.org/mailman/listinfo/zeromq-dev >
_______________________________________________ zeromq-dev mailing list [email protected] https://lists.zeromq.org/mailman/listinfo/zeromq-dev
