[Spread-users] Session disconnect

[Theo Schlossnagle]

On Friday, March 8, 2002, at 09:20 AM, koorosh.alahiari at ids.allianz.com 
wrote:
> I was wondering if anyone could explain to me the
> reasoning behind the forced shut down of slow
> receivers. This kinds of defeats the object of
> Reliable Multicast data delivery.
>
> I was told on a previous mail that spread
> drops clients BUT it does NOT drop messages
> so whenever my receivers were dropped I
> tried an immediate reconnection and found
> that about 30% of my messages were lost.
>
> I would rather avoid implementing an ACK
> mechanism since this would slow down the
> very respectable performance of spread!

You don't need to implement an ACK mechanism.  Spread provides you with 
this information.

Spread will notify the _sender_ that the group has changed when your 
receiver is disconnected.  so you didn't "loose" any messages.  You 
should have been aware that you were sending them to a group that didn't 
contain the member you were expecting to hear them

Spread's group semantics provide a powerful and sufficient mechanism for 
implementing application-level reliable delivery.  Spread itself, only 
implements daemon-to-daemon (network) reliable multicast.

--
Theo Schlossnagle
1024D/82844984/95FD 30F1 489E 4613 F22E  491A 7E88 364C 8284 4984
2047R/33131B65/71 F7 95 64 49 76 5D BA  3D 90 B9 9F BE 27 24 E7