Path: utzoo!mnetor!uunet!husc6!mailrus!ames!amdahl!acs From: acs@amdahl.uts.amdahl.com (Tony Sumrall) Newsgroups: comp.sys.amiga.tech Subject: Re: What about the serial port IPC discussion? Message-ID: <31046@amdahl.uts.amdahl.com> Date: 7 May 88 22:16:34 GMT References: <30731@amdahl.uts.amdahl.com> <856@imagine.PAWL.RPI.EDU> Reply-To: acs@amdahl.uts.amdahl.com (Tony Sumrall) Distribution: na Organization: Amdahl Corporation, Sunnyvale CA Lines: 27 In article <856@imagine.PAWL.RPI.EDU> jesup@pawl12.pawl.rpi.edu (Randell E. Jesup) writes: > Well, it was a big item of discussion at the Devcon, I was on >the panel (suprise), as was Bryce (suprise). It seems there will be two >levels: a low-level mapper in the serial.device that bryce is working on, >that maps unit numbers to other devices, and a name mapping utility, that >allows you to tell it you want a modem (or xyzvax via direct connect,...). Well, this is close but not exactly on target. The discussion to which I was referring specified that an IPC handler should be created for the serial port. Upon reflection now, though, it seems that the serial device would serve just as well as an IPC server if it provides for what I called a "listener". This differs from simply opening the serial device in shared mode in that everyone that has a read up receives *all* of the data that comes in across the serial port (instead of a chunk going to this user and a chunk going to that user). Does this sound right to you Doug (Merritt--the other primary "contributor" to the discussion)? BTW, Randell, I got your e-mail...thanks and congrats on the new job! > // Randell Jesup Lunge Software Development -- Tony Sumrall acs@amdahl.uts.amdahl.com <=> amdahl!acs [ Opinions expressed herein are the author's and should not be construed to reflect the views of Amdahl Corp. ]