Path: utzoo!utgpu!news-server.csri.toronto.edu!rutgers!att!linac!uwm.edu!wuarchive!usc!apple!lsr
From: lsr@Apple.COM (Larry Rosenstein)
Newsgroups: comp.sys.mac.system
Subject: Re: System 7.0 era
Keywords: IAC
Message-ID: <52764@apple.Apple.COM>
Date: 11 May 91 19:24:45 GMT
References: <1991May10.140513.692@magnus.acs.ohio-state.edu>
Distribution: usa
Organization: Object-Based Systems, Apple Computer, Inc.
Lines: 28

In article <1991May10.140513.692@magnus.acs.ohio-state.edu> bgrubb@magnus.acs.ohio-state.edu writes:

>And I forgot to tell where I got my information from so here goes;
>The above was baced on an article in May 91 issue of MacUser called
>"Applications are Talking Too" by Michael Swaine pg 239
>And the article stated that since a part of IAC (publish and subscribe)
>(I think) was not standerdized, "programs made by the same company would
>communicate better with each other then with those from other companies."
>(The above is a paraquote)

First you forgot the beginning of the sentence: "Unlike AppleEvents, its
protcols are not standardized by Apple...".  Second, you forgot
the following sentence: "This is called proprietary IAC."

Swaine is talking about low-level IAC here, not publish and subscribe.
The low-level IAC mechanism can be used to send any set of bytes from one
place to another.  Developers can take a proprietary approach and define
their own format for these bytes if they choose.

But Apple has also defined AppleEvents which are a standard language for
communicating between applications.  Publish and subscribe is implemented
(in part) using AppleEvents.  

-- 
Larry Rosenstein, Apple Computer, Inc.

lsr@apple.com
(or AppleLink: Rosenstein1)