Socket Comm Sequence Issue

[Brian Yennie]

Yup! I said it backwards, but coded it out that way... =). The only 
extra trick is if you don't know whether you are App #1 or App #2. But 
then, just try to be Application #2 (by talking), and if the connect 
fails, you're #1 (and so launch #2)...

> If app 1 launches app 2, app 2 should initiate the conversation, since 
> app 1 should be ready to listen by the time it launches app 2, whereas 
> app 1 would not know how long it was going to take app 2 to reach the 
> point where it is listening.