[zeromq-dev] ZMTP 3.0 Status: Sharing Single TCP connection (Example code ?)

[Pieter Hintjens]

ZMTP 3.0 does not do connection multiplexing, which would indeed
interfere with TCP, apart from being nasty at the protocol and error
handling levels too.

What it does is port sharing, so multiple servers can "bind" to the
same port. In fact they talk to a proxy that does the bind one time,
and which handles the initial negotiation and then switches the
connection over to the server (using the resource name specified in
the connection request).

Martin Sustrik already demonstrated this some time ago, I put it into
ZMTP now because it's needed for realistic Internet use (along with
security).

-Pieter

On Fri, Jun 7, 2013 at 11:25 PM, Justin Karneges <justin at affinix.com> wrote:
> On 06/07/2013 02:02 PM, Pieter Hintjens wrote:
>> On Fri, Jun 7, 2013 at 8:22 PM, Yannick Koehler <yannick at koehler.name> wrote:
>>
>>> ZMTP doesn't allow multiplexing PUB/SUB and REQ/REP over the same single TCP
>>> connection simulteanously?  I thought the Resource concept was about that.
>>
>> Yes, it will allow this. Libzmq doesn't implement that yet. However it
>> doesn't change the fact you need a full ZMTP stack at both sides. If
>> one side is libzmq and the other is a web server, you have a slight
>> problem.
>
> Hmm, wouldn't multiplexing defeat the handy queuing & back-pressure
> behavior provided by TCP?
>
> Justin
>
> _______________________________________________
> zeromq-dev mailing list
> zeromq-dev at lists.zeromq.org
> http://lists.zeromq.org/mailman/listinfo/zeromq-dev