Path: utzoo!mnetor!uunet!husc6!bbn!rochester!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: IPC - IPCMessage and Networks Message-ID: <867@imagine.PAWL.RPI.EDU> Date: 8 May 88 06:13:50 GMT References: <5699@well.UUCP> <9131@agate.BERKELEY.EDU> <5819@well.UUCP> <5872@well.UUCP> <1929@sugar.UUCP> <5896@well.UUCP> Sender: news@imagine.PAWL.RPI.EDU Reply-To: jesup@pawl23.pawl.rpi.edu (Randell E. Jesup) Organization: RPI Public Access Workstation Lab - Troy, NY Lines: 21 Keywords: IPC, standard, network In article <5896@well.UUCP> shf@well.UUCP (Stuart H. Ferguson) writes: >Named message ports provide a >one-to-one mapping between names and ports, where the names are just >something that the programmer made up for their program. This is like >the White Pages in that you have to know the specific name of the server >you want to use. The object-oriented approach uses a many-to-one >mapping between services and ports, where services are an abstract >description of an operation that a server will perform. This is like >the Yellow Pages in that you use the service you want performed to look >up the message port. Sounds like a job for SUPER-MAPPER! Seriously, the name mapper I'm working on (mainly for expansion serial ports) would be perfect for the Yellow Pages style lookup, since I generalized for use with software, as well as hardware. // 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 :-)