Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!uwm.edu!fps.mcw.edu!myamiga!smp
From: smp@myamiga.UUCP (Steve Palm)
Newsgroups: comp.sys.amiga.tech
Subject: Re: Multi serial/parallel ports
Message-ID: <91.272FAC57@myamiga.UUCP>
Date: 1 Nov 90 03:58:44 GMT
Organization: The Siberian Amiga --- Sault Ste. Marie, MI
Lines: 31


 In article <13918@mcdphx.phx.mcd.mot.com>, teroach writes:
 
 DK> The proper way:
 DK> 
 DK>    The dialin (monitor) program periodically wakes up, allocates the
 DK> serial device for exclusive use (if refused, port is busy with dialout
 DK> program), and asks the state of the DTR line.  If busy or DTR inactive,
 DK> go back to sleep otherwise proceed with the dialin program. 

 In my opinion, that is not proper.  First of all, the program waiting for the
 incoming calls should ALWAYS be running. The dialout program would only come
 up as needed, if ever.  Secondly, these two programs are not related, so they
 should not be thought of as being able to pass information to each other.
 
 The dialout program should have a flag asking whether or not you wish to muck
 around with the DTR.  If you say YES and have other programs running that
 would be adversely affected by this, you are responsible.  I don't feel that
 you should have to have exclusive access to the serial port to toggle DTR.
 Nor do I think you should have to do a open/close on the device to achieve
 this.  It is utter nonsense to have to go to the hardware for this function.
 
 These are my opinions, so you may very well (and probably will) disagree
 with me.


--  
     ///  AMIGA: | Steve Palm, Sysop of FidoNet node 1:11/16
    ///  FOR THE | UUCP: {gatech,ames,rutgers}!ncar!asuvax!stjhmc!myamiga!smp
\\\///  CREATIVE | INTERNET: [not yet available]
 \XX/     MIND   |_________________________________________________________