[prev in list] [next in list] [prev in thread] [next in thread]
List: zeromq-dev
Subject: Re: [zeromq-dev] Can ROUTER multiplex REQ/REP and PUB/SUB?
From: Mark Botner <mbotner () gmail ! com>
Date: 2019-03-27 13:53:53
Message-ID: CAO=G9=aYnV769LseKjAbHUWR606B4a42MNWMx7B=gu2M0G_AGQ () mail ! gmail ! com
[Download RAW message or body]
[Attachment #2 (multipart/alternative)]
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 <jake.cobb@gmail.com> 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
> zeromq-dev@lists.zeromq.org
> https://lists.zeromq.org/mailman/listinfo/zeromq-dev
>
[Attachment #5 (text/html)]
<div dir="ltr"><div dir="ltr"><div dir="ltr"><div class="gmail_default" \
style="font-size:large">According to the reference pages: <a \
href="http://api.zeromq.org/4-2:zmq-socket">http://api.zeromq.org/4-2:zmq-socket</a></div><div \
class="gmail_default" style="font-size:large"><br></div><div class="gmail_default" \
style="font-size:large"><table class="gmail-wiki-content-table" \
style="empty-cells:show;border-collapse:collapse;border-spacing:0px;margin:0.5em \
auto;color:rgb(0,0,0);font-family:verdana,arial,helvetica,sans-serif;font-size:13.12px"><tbody><tr><th \
colspan="2" style="border:1px solid rgb(136,136,136);padding:0.3em \
0.7em;background-color:rgb(238,238,238)">Summary of ZMQ_ROUTER \
characteristics</th></tr><tr><td style="border:1px solid \
rgb(136,136,136);padding:0.3em 0.7em">Compatible peer sockets</td><td \
style="border:1px solid rgb(136,136,136);padding:0.3em 0.7em"><em>ZMQ_DEALER</em>, \
<em>ZMQ_REQ</em>, <em>ZMQ_ROUTER<br></em></td></tr></tbody></table></div><div \
class="gmail_default" style="font-size:large"><br></div><div class="gmail_default" \
style="font-size:large">So I don't think the design you are looking at will \
work.</div><div class="gmail_default" style="font-size:large"><br></div><div \
class="gmail_default" style="font-size:large"><br></div><div class="gmail_default" \
style="font-size:large">Mark</div></div></div></div><br><div class="gmail_quote"><div \
dir="ltr" class="gmail_attr">On Wed, Mar 27, 2019 at 8:50 AM Jake <<a \
href="mailto:jake.cobb@gmail.com">jake.cobb@gmail.com</a>> \
wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px \
0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr">I \
currently have a system that has two public ports, \
facilitating:<div><br></div><div>REQ <-- tcp --> ROUTER <-- proxy --> \
DEALER <-- inproc --> \
REP</div><div><br></div><div>and</div><div><br></div><div>SUB <-- tcp --> PUB \
(various internal sinks supplying events)</div><div><br></div><div>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:</div><div><br></div><div><br></div><div><font face="monospace, monospace">REQ \
--\ /--ROUTER--DEALER--REP </font></div><div><font \
face="monospace, monospace"> ROUTER</font></div><div><font face="monospace, \
monospace">SUB --/ \--PUB</font></div><div><font face="monospace, \
monospace"><br></font></div><div><font face="arial, helvetica, sans-serif">So there \
is only one TCP port listening required, a common CURVE configuration point, \
etc?</font></div><div><font face="arial, helvetica, \
sans-serif"><br></font></div><div><font face="arial, helvetica, \
sans-serif">-Jake</font></div></div> \
_______________________________________________<br> zeromq-dev mailing list<br>
<a href="mailto:zeromq-dev@lists.zeromq.org" \
target="_blank">zeromq-dev@lists.zeromq.org</a><br> <a \
href="https://lists.zeromq.org/mailman/listinfo/zeromq-dev" rel="noreferrer" \
target="_blank">https://lists.zeromq.org/mailman/listinfo/zeromq-dev</a><br> \
</blockquote></div>
_______________________________________________
zeromq-dev mailing list
zeromq-dev@lists.zeromq.org
https://lists.zeromq.org/mailman/listinfo/zeromq-dev
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic