> You may want to do downloads with UDP, and have the client send a "whoa,
> I'm losing too many packets; throttle back n%" when things start getting
> lossy (with perhaps a creep-back-up timer, too.)
As long as your window size is set greater than or equal to the
bandwidth delay product, that's exactly what TCP achieves. Except
that it does it with at least 20 years of experience behind it. ;-}
In general, trying to reproduce what TCP does on lossy networks using
any datagram protocol is a losing proposition, usually because most
implementors get the congestion control aspects wrong the first half
dozen or so times they try to implement it.
As for running multiple streams (a la Netscrape), that's not necessary
unless the window sizes are pathetically small. In that case, the
right answer is to make sure that the large window size option is
implemented instead. The TCP algorithms are designed to fill all
available bandwidth in the face of lossy and congested pipes.
--
James Carlson, Software Architect <[EMAIL PROTECTED]>
IronBridge Networks / 55 Hayden Avenue 71.246W Vox: +1 781 372 8132
Lexington MA 02421-7996 / USA 42.423N Fax: +1 781 372 8090
"PPP Design and Debugging" --- http://people.ne.mediaone.net/carlson/ppp
