[comp.sys.mac.programmer] Communicating between separate pieces of software with

ech@cbnewsk.ATT.COM (ned.horvath) (06/14/89)

Rich Siegel:
> 	For example, suppose you have an INIT and a cdev that need to
> share information with one another? How do you propose to have them
> communicate? Remember, there's no low memory you can use, and there's
> no place to place a base register...

Tim Maroney:
> ...install a module-independent
> dispatching routine.  The glue would be a simple routine that stores
> pairs of (signature,dispatch), keyed by "signature", where signature is
> a four-byte creator ID registered with Apple (and presumably used for
> one or more of your files) and dispatch is a function pointer
> indicating a function dispatch switch where the first argument is a
> numerical routine selector...

Well, we haven't seen the details of the System 7.0 Inter-Application
Communications (IAC) facilities, but what WAS discussed at the Developer
Conference is very similar to what Tim proposes.  In particular, the
notion of message queues, labelled (among other stuff) with creator IDs,
is likely to be built in at some level.  There's no functional distinction
between "routine selector 4" and a message of type "defenestrate."

Of course, that's system 7...

=Ned Horvath=