Re: [jgroups-users] NAKACK seems unnecessary with UDP ip_mcast=false

If you send a message to the entire cluster (msg.dest == null), then 
NAKACK will always be used regardless of whether UDP.ip_mcast is true or 
false.

The ip_mcast attr only governs how the *transport* (UDP) will send the 
message true: as an IP multicast, false: as N-1 unicast datagrams).

UNICAST is never involved here, as the message is still a 'multicast' 
message, even if we send it as N-1 unicast datagrams.

On 18/10/16 22:39, Questions/problems related to using JGroups wrote:
> I understand that NAKACK is necessary when I'm doing a
> channel.send(new Message(null, ...)) but it seems strange to have
> NAKACK when I also have the UDP channel sending out channel messages
> as unicast to each view member.
>
> Seems to me that a UNICAST ip_mcast=false setting would make more
> sense.  Then you could get rid of NAKACK and do the reliability at
> the same time.  Is there something that I'm missing here that would
> invalidate this?
>
> Thanks, gray


-- 
Bela Ban, JGroups lead (http://www.jgroups.org)


------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most 
engaging tech sites, SlashDot.org! http://sdm.link/slashdot