Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!sdd.hp.com!hplabs!hpfcso!hpfcdc!koren
From: koren@hpfcdc.HP.COM (Steve Koren)
Newsgroups: comp.sys.amiga.tech
Subject: Re: Re: PIPEing from ser:
Message-ID: <11640032@hpfcdc.HP.COM>
Date: 25 Nov 90 07:49:03 GMT
References: <1990Nov16.104712.20944@phoenix.pub.uu.oz.au>
Organization: HP Fort Collins, Co.
Lines: 21



> The whole point of the discussion is quite simple: a call to Write()
> will take as long as it pleases to take.  If you happen to be a terminal
> program, and it takes 10 hours for the user to wake up the next morning
> and stick the right disk in, chances are the other end of session has
> timed out on you.

Well, yeah, it goes without saying that you've gotta stick the disk
in the drive :-) - but even if the floppy takes several minutes to
write the data, that'll work just fine.  I use cts/rts all the time
and it works like a charm.  It will, as I mentioned before, allow
receiving data to a floppy from a high speed serial line.  I've done
this at 14400+ bps with no problems.  Granted, the other system will
have to pause sometimes to wait for the floppy, but no data is lost.
If your remote system give up *that* fast, I'd think something would
be wrong with it.  Similarly, as long as the consumer end of the pipe
got around to consuming a block every few minutes, things should
work just fine.

   - steve