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

[Yannick Koehler]

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.

My understanding is that resource map to thread which open PUB/SUB sockets
or REQ/REP type of socket and the ZMTP transport both to the same endpoint
using a single TCP connection.

I will go re-read the protocol again, but there is also no implementation
of that protocol yet?


2013/6/7 Pieter Hintjens <ph at imatix.com>

> On Fri, Jun 7, 2013 at 5:40 PM, Yannick Koehler <yannick at koehler.name>
> wrote:
>
> > Ok, so let's say I have a bridge, so I have internally multiple TCP
> > connections going towards my bridge which then has to multiplex all
> > those zeroMQ TCP connection into the websockets protocol.  The
> > websockets protocol doesn't have sub-channel, I will then have to
> > build a multiplexing/demultiplexing protocols.
>
> Yes, and you will also have to deal with the semantics of patterns in
> the web server. There's no transport layer magic that will turn a HTTP
> server into a pub-sub engine. Who is doing the mapping?
>
> > My understanding is that ZMTP 3.0 is such a thing
>
> That would be a wrong understanding.
>
> > ...
> > Does that make sense?
>
> I'm sure your problem makes sense, but it seems to me you want
> professional advice for free. That is not the purpose of this list.
>
> If you want to speak with a professional ZeroMQ architect, ask it, and
> you'll get offers. If you want this list to help you, first learn
> enough to ask questions that can be answered precisely.
>
> "Does ZeroMQ solve my <insert highly specific use-case and BTW
> performance!>" is not the right question.
>
> -
> Pieter
> _______________________________________________
> zeromq-dev mailing list
> zeromq-dev at lists.zeromq.org
> http://lists.zeromq.org/mailman/listinfo/zeromq-dev
>



-- 
Yannick Koehler
Courriel: yannick at koehler.name
Blog: http://corbeillepensees.blogspot.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.zeromq.org/pipermail/zeromq-dev/attachments/20130607/b09bce05/attachment.htm>