On Sun, Sep 07, 2003 at 10:48:50PM +0200, BRANE wrote:
> ----- Original Message ----- 
> From: "Peter Graf" <[EMAIL PROTECTED]>
> Sent: Sunday, September 07, 2003 9:53 PM
> Subject: Re: [ql-developers] Massive amount of job state transitions and
> re-scheduling

> > Simple example: A M$ or Unix machine sends a file to the QDOS machine via
> > TCP. It will send one or two packets, then stop and wait for ACK. Further
> > packets will only be sent after further ACKs. Your ACKs can only be
> > generated in 50 Hz rhythm, so packets will crawl one-by-one in 50 Hz
> > rhythm. (Or two-by-two, if you're lucky.)
> AFAIK with TCP/IP this is negotiable. There is no need for such small
> window...

don't forget this is a rather simple TCP/IP implementation and apparently
it is already hard enough to make the simplest variant working reliably
with the garden variety of TCP/IP implementations out there.


Reply via email to