[zeromq-dev] Announcing ZFL

[Martin Sustrik]

On 08/21/2010 07:57 PM, Pieter Hintjens wrote:
> On Sat, Aug 21, 2010 at 7:41 PM, Martin Sustrik<sustrik at 250bpm.com>  wrote:
>
>> Yes. It's the broker scenario. Say different services on the corporate
>> network, all funneled via a single executable (the broker).
>
> Right.  Problem is that as soon as you start with a broker scenario
> you need a more sophisticated protocol.  It's not difficult as such
> but it's a different direction than multiplexing.

Multiplexing on a single destination port. Different source ports 
though. So the protocol stays exactly the same.

>> This seems a bit pathological with current "port per dataflow" approach. On
>> the other hand, a feature I have in mind for a long time is "TCP subports"
>> -- say tcp://192.168.0.111:5555:45 -- to allow multiple streams to flow via
>> a single open port.
>
> Multiplexing across TCP connections, right?
>
> You could use names rather than numbers for the substream.  That gives
> you a naming flexibility similar to what we have with inproc/ipc, and
> possibly some kind of service abstraction without a name service.
>
> Definitely an interesting idea and one we should look into.

Yes, it's kind on back of my mind for a long time. Every time I think of 
using 0MQ behing corporate firewall it strikes back.

Martin