Path: utzoo!news-server.csri.toronto.edu!cs.utexas.edu!wuarchive!uwm.edu!bionet!agate!ucbvax!pasteur!cory.Berkeley.EDU!navas
From: navas@cory.Berkeley.EDU (David C. Navas)
Newsgroups: comp.sys.amiga.programmer
Subject: Re: Inter process communication
Message-ID: <11854@pasteur.Berkeley.EDU>
Date: 10 Mar 91 19:16:44 GMT
References: <19579@cbmvax.commodore.com> <10708@dog.ee.lbl.gov>
Sender: news@pasteur.Berkeley.EDU
Reply-To: navas@cory.Berkeley.EDU
Lines: 28

In article <> jnmoyne@lbl.gov (Jean-Noel MOYNE) writes:
>
>       There is a good internal message system in the OS of the Amiga (in 
>the exec.lib to be precise). Message passing using exec works very well, 
>and is quite straight forward to understand and implement (see the RKM for 
>help).

Except for one rather hairy problem -- disappearing server ports...

>       But there is another solution: Pete Goodeve has written a package 
>called IPC for "Inter Process Communication" (how did you guess ? (-:). 
>
>PS: Pete's EMail is goodeve@violet.berkeley.edu

Does that work as well?  I've always mailed pete@violet.berkeley.edu, and
even his finger givs his login name as "pete" not "goodeve"?

PPIPC (Pete & Peter's IPC) is very good for server-client modelled
communications, can get hairy for one-to-many broadcasts, and still doesn't
solve the disappearing ReplyMsg port, but I use it *always* instead of the
regular calls, because of the added protection they provide.
At least one other person on the net has used it in his scientific
application, but I'll let him discuss what he thinks about it...


David Navas                                   navas@cory.berkeley.edu
"Saddam was a man who trusted only himself.  Seems like he trusted one man
 too many..." [Also try c186br@holden, c260-ay@ara and c184-ap@torus]