Socket Tutorial Guidelines [was: thank you notes]

[Rob Cozens]

>What should a tutorial be like?

That's up to the author, Dar.

The best example that comes to my mind is the Apple Event Primer 
stack from Apple.  I have it opened here now...

"This stack is an introduction to HyperCard's new ability to 
communicate with other applications and other Macintosh computers via 
Apple events."

The sections are:

* Setting up
* Choosing
* Asking
* Telling
* Conversing
* Exploring

eMail me privately if you would like a copy (you should be able to 
open it in RunRev).

Basically, I would like to see the ins & outs and dos & don'ts of 
establishing interprocess communication via sockets, eg: how do I 
establish communication & exchange data between two or more Rev 
standalones.

Perhaps this is a good time to ask for confirmation of what I think I know:

I have selected socket communication as the preferred approach to 
interapplication communication because it is the only approach I know 
of that works on all platforms, and over the Internet as well. 
Obviously, scripting Apple event handlers does one little good when 
it's time to port to Unix/Windows.  Am I losing any significant 
timing and/or data passing capacity advantages of platform-specific 
avenues of interprocess communication?

In other words, is there any intrinsic reason for using Apple events 
on Macs and  their equivalent on Windows vs using sockets on both?
-- 

Rob Cozens
CCW, Serendipity Software Company
http://www.oenolog.com/who.htm

"And I, which was two fooles, do so grow three;
Who are a little wise, the best fooles bee."

from "The Triple Foole" by John Donne (1572-1631)