home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!zaphod.mps.ohio-state.edu!wupost!spool.mu.edu!yale.edu!jvnc.net!newsserver.jvnc.net!rutgers!psuvax1!postscript.cs.psu.edu!fenner
- From: fenner@postscript.cs.psu.edu (Bill Fenner)
- Newsgroups: comp.dcom.modems
- Subject: Re: ZyXEL voice and flow control
- Keywords: ZyXEL voice flow control
- Message-ID: <C0Goy4.8A0@cs.psu.edu>
- Date: 7 Jan 93 02:15:40 GMT
- References: <rkimball.726258443@athena> <2B4AF74B.602A@telly.on.ca> <C0GHIz.MoJ@wsrcc.com>
- Sender: news@cs.psu.edu (Usenet)
- Organization: Penn State Computer Science
- Lines: 18
- Nntp-Posting-Host: postscript.cs.psu.edu
-
- In article <C0GHIz.MoJ@wsrcc.com> wolfgang@wsrcc.com (Wolfgang S. Rupprecht) writes:
- |Having to deal with software flow control forces one to write fairly
- |inefficient code. One can't just do a single "write(buffer, 1024)"
- |and be done with it.
-
- Hardly; XON/XOFF is the TTY driver's job. Set IXON, and feel free to write
- gobs and gobs of data and let the TTY driver worry about flow control.
-
- Of course, if you're on an operating system without a TTY driver, then yes,
- you have to do it yourself.
-
- |I don't see how any person could claim that byte-at-time writes with
- |intervening reads are "reasonable".
-
- Since this is only necessary under an unreasonable operating system anyway,
- I don't see the problem.
-
- Bill
-