[Spread-users] Question about thread-safety

[John Schultz]

Here is a link to a detailed discussion of connection resiliency and
complex flow control:

http://lists.spread.org/pipermail/spread-users/2002-March/000655.html

I think, unless your application absolutely cannot handle failing (which
would be a BAD thing), that the simple flow control I suggested would be
more than good enough for your application.

-- 
John Schultz
Co-Founder, Lead Engineer
D-Fusion, Inc. (http://www.d-fusion.net)
Phn: 443-838-2200 Fax: 707-885-1055

White Stuart - stwhit wrote:

 > Thanks again John.  This discussion has been very helpful!
 >
 > In your note, you state "the #1 reason for a closed connection is either
 > your app is sending too many messages or not receiving fast enough".
 >
 > I understand how to control the "sending too many messages" - by 
enforcing a
 > maximum number of outstanding messages as you described below.
 >
 > That solves half the problem.  How do I solve the other half?  (if my 
app is
 > not receiving fast enough).  It is undesireable for my processes to 
simply
 > get kicked out of the group because they can't keep up with the other
 > processes.  Is there a way I can handle this more gracefully?  Perhaps
 > detect that one of the processes is getting overwhelmed and instruct the
 > other processes to stop sending until the slow process catches up?
 >
 > How do other spread applications handle this?
 >
 > Thanks again!
 >