[zeromq-dev] Can't bind same ZMQ_UP/DOWNSTREAM multiple times.
Jon Dyte
jon at totient.co.uk
Thu Aug 19 22:11:34 CEST 2010
Oliver Smith wrote:
> Martin Sustrik said the following on 8/19/2010 7:19 AM:
>
>> Binding several sockets to a TCP port to get a multicast delivery is
>> something TCP doesn't support. You'll either have to do with a device in
>> the middle or use IP multicast (via PGM) which effectively turns your
>> switch into the device. Using IP multicast has its own set of problems
>> though.
>>
>>
> I understand the TCP component there, but again: ZeroMQ sockets aren't
> sockets.
>
> a/ I was trying to use inproc://
> b/ All of my attempts to service the socket are on the same context.
>
> Currently the pipeline pattern allows you to connect 1-N, but it doesn't
> let you connect N-to-N because of a TCP issue?
>
>
>
I'm reading this thread late on, but isn't this what the streamer is
for, assuming it is a pipeline, not req-rep?
so if you have 3 threads producing data and and 6 threads doing
subsequent work (that was the jpg attached earlier in the thread)
don't you just need to put a streamer inbetween ?
so the 3 producers connect to the streamer and write to it, and the 6
workers connect and read from it
so 10 threads in this example?
> _______________________________________________
> zeromq-dev mailing list
> zeromq-dev at lists.zeromq.org
> http://lists.zeromq.org/mailman/listinfo/zeromq-dev
>
>
More information about the zeromq-dev
mailing list