[zeromq-dev] [PATCH] Resolve issue 104, ZMQ_MCAST_LOOP enabled by default

[Matt Weinstein]

(Sorry all, that last email should have gone to Steve.  Got snagged by Reply-to: :-( )

On Apr 21, 2011, at 12:28 PM, Matt Weinstein wrote:

> Greetings, I hope all is well with you.
> 
> I've returned to working on the network portion of our system, and am starting to use OpenPGM over ØMQ.
> 
> I understand the stack limitation relating to loopback.
> 
> Of course you could create a special purpose dependency in the app.  However, I don't see how to clean this up without using either locks or another context switch.
> 
> Why not add another OPT_ field?  RFC3208 _is_ still marked as experimental... :-)
> 
> Just provide MCAST NAK capability, and submit as a change to the RFC?  e.g. In the event the network stack does not permit ..., ... MAY ... use OPT_NAKP2P ... Packets SHALL be ignored by all other non-addressed .. ?
> 
> RSVP,
> 
> Thanks / Arigato,
> 
> Matt
> 
> On Oct 23, 2010, at 9:48 PM, Steven McCoy wrote:
> 
>> On 23 October 2010 23:15, Martin Sustrik <sustrik at 250bpm.com> wrote:
>> 2. Fix the faulty behaviour of multicast+loopback either on OpenPGM or 0MQ level.
>> 
>> 
>> It's a PGM protocol limitation on current IP stack implementations and so if solvable only solvable inside ØMQ, however the transport would no longer be "PGM" and so it is better to defer it higher up and have the developer swap to IPC.
>> 
>> -- 
>> Steve-o
>> _______________________________________________
>> zeromq-dev mailing list
>> zeromq-dev at lists.zeromq.org
>> http://lists.zeromq.org/mailman/listinfo/zeromq-dev
> 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.zeromq.org/pipermail/zeromq-dev/attachments/20110421/c15e05d5/attachment.htm>