Path: utzoo!attcan!uunet!tut.cis.ohio-state.edu!ucbvax!agate!shelby!daemon
From: lane@sumex-aim.stanford.edu (Christopher Lane)
Newsgroups: comp.sys.next
Subject: Callbacks via Speaker/Listener
Message-ID: <2189@shelby.Stanford.EDU>
Date: 28 Jun 90 18:30:58 GMT
Sender: daemon@shelby.Stanford.EDU
Lines: 20

I have an application (yet to be built) that I want multiple other
applications to message (via Speaker/Listener) and I not only want to respond
to those messages but keep track of who sent them so that when a later event
occurs, I can 'call back' to specific applications with a message via
Speaker/Listener.

I see no way in the documentation for a Speaker/Listener style method to find
out anything about the remote sender.  My guess is I could do what I want by
dropping down to the MACH/C level but I'd much prefer to do via methods.  I
could also do this by passing the application name/port as a message argument
everytime but that offends my sense of esthetics.

What are others doing about call backs?  Some combination of specializing
messageReceived: and a global is the best approach I can conjure and I'm not
too sure about it.

Thanks for any suggestions,

- Christopher
-------