Socket Comm Sequence Issue
chipp at chipp.com
Fri Apr 15 04:44:02 CDT 2005
Perhaps a traditional client/server model, where one is always listening
and the other talking? Business logic at both ends should enable you to
do a lot.
If that won't do, then perhaps the old 'pass messages with a small text
file' would help 'boot things'.
Ken Ray wrote:
> I'm trying to get two apps to talk to each other over sockets on OS X, which
> means that both apps need to be in "listening" mode as well as "speaking"
> mode. The relevant code I'm using for testing this right now is shown below,
> and doesn't trap for errors or messages that I'm not interested in:
More information about the use-livecode