Path: utzoo!attcan!utgpu!news-server.csri.toronto.edu!mailrus!uflorida!mephisto!psuvax1!swatsun!jackiw From: jackiw@cs.swarthmore.edu (Nick Jackiw) Newsgroups: comp.sys.mac.programmer Subject: Re: Inter-Process Communication Message-ID: Date: 5 Aug 90 16:04:12 GMT References: <1990Aug4.063810.14788@cs.uoregon.edu> <2286@polari.UUCP> Reply-To: jackiw@cs.swarthmore.edu (Nick Jackiw) Organization: Visual Geometry Project, Swarthmore College, PA Lines: 39 robert@polari.UUCP (robert) writes: .> .> > As part of my research I have to write a bunch of applications that .> > can talk to each other ... I haven't found *any* reference to this .> > ... I was essentially told: Wait for System 7. .> .> There were several articles in MacTutor written by Frank Alviani and .> Paul Snively on implementing an IAC driver on the Mac. .> [MacTutor references deleted] .> .> You also might want to check out: .> [Wait for System 7 references deleted] The MacTutor stuff, which is excellent, is probably more general than you need, if your suite of programs require only a rigidly specified communication protocol. Its worth reading anyway, if you're thinking of a driver-based IPC. You may also want to consider doing it with Appletalk. An oft-overlooked an oft-overlooked feature of Appletalk is that it works fine even if you aren't connected to a net: each program can request a socket on the same machine, and then communicate with others (also on that machine) through that socket. Neither of these schemes has System 7-IPC's advantage of having a nicely developed protocol for IPC between applications of which only one is currently running. Whether this feature is relevant to your application is up to you, of course. feature of A -- ------------------------ Nick Jackiw jackiw@cs.swarthmore.edu "Every minute of the future Visual Geometry Project jackiw@swarthmr.bitnet is a memory of the past." Swarthmore College, PA 19081-1397 -Laivach