[Spread-users] Spread and reliable message communication

Jim Vickroy Jim.Vickroy at noaa.gov
Fri Aug 8 15:58:10 EDT 2003

Tim Peters wrote:

> [snip]

> That's where you're off:  Spread leaves flow control to the application.  Do
> a google search on, e.g.,
>     spread-users flow control
> for some good prior discussions about this.  In the app we wrote the Python
> wrapper to support, we do a number of things to protect against servers
> outrunning clients.  One was to build our own "chunking" layer on top of
> Spread messages, to get more data sent per msg (Spread receivers balk based
> on number of unread messages pending, independent of their aggregate size);
> our app had a very large number of very small messages otherwise.  Another
> was to implement a recovery protocol, so that when a client disconnects (for
> whatever reason), it can ask the server to resend from the point of the last
> message received.


Did you intend to say: "... it can ask the **sender** to resend from the point
of ..."
rather than: "... it can ask the server to resend from the point of ..."?

If not, how can the (Spread) server do this?

-- jv

>  Another is that, in part of the app, a thread does
> nothing but call SP_receive in a loop, queueing the read messages for later
> action.


More information about the Spread-users mailing list