Path: utzoo!mnetor!uunet!husc6!bloom-beacon!mit-eddie!uw-beaver!cornell!batcomputer!itsgw!imagine!pawl23.pawl.rpi.edu!jesup From: jesup@pawl23.pawl.rpi.edu (Randell E. Jesup) Newsgroups: comp.sys.amiga.tech Subject: Re: What about the serial port IPC discussion? Message-ID: <868@imagine.PAWL.RPI.EDU> Date: 8 May 88 06:22:33 GMT References: <30731@amdahl.uts.amdahl.com> <856@imagine.PAWL.RPI.EDU> <31046@amdahl.uts.amdahl.com> Sender: news@imagine.PAWL.RPI.EDU Reply-To: jesup@pawl23.pawl.rpi.edu (Randell E. Jesup) Distribution: na Organization: RPI Public Access Workstation Lab - Troy, NY Lines: 20 In article <31046@amdahl.uts.amdahl.com> acs@amdahl.uts.amdahl.com (Tony Sumrall) writes: >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). Either a) create a second-level handler that is the one that talks to the serial.device, then clones off copies for everyone, or b) create a fake serial.device (named something else), that took stuff like a serial device, and passed them all to/from the serial device, except that it cloned the shared reads. You could register this as a serial device with the name- mapper, so programs that know nothing of this whole concept would then work with it, whereas option a requires programs to be written to take advantage of this. // Randell Jesup Lunge Software Development // Dedicated Amiga Programmer 13 Frear Ave, Troy, NY 12180 \\// beowulf!lunge!jesup@steinmetz.UUCP (518) 272-2942 \/ (uunet!steinmetz!beowulf!lunge!jesup) BIX: rjesup (-: The Few, The Proud, The Architects of the RPM40 40MIPS CMOS Micro :-)