On Jun 26, 2005, at 4:34 PM, Dar Scott wrote:
The second one (in the netConnectOne handler) can cause nested
responses, so if some of those variables are global then the values
will get scrambled. This might cause both responses to go to only one
client.
I didn't word that well.
The 'wait with messages' in the middle of the accept message handler
can allow a new accept message to be processed in the middle of
another. Suppose connections come in from client A and then client B.
It is possible for the first half of execution of netConnectOne is
executed for A, then the first half for B, then the second half for B,
then the second half for A.
Dar
--
**********************************************
DSC (Dar Scott Consulting & Dar's Lab)
http://www.swcp.com/dsc/
Programming and software
**********************************************
_______________________________________________
use-revolution mailing list
[email protected]
Please visit this url to subscribe, unsubscribe and manage your subscription
preferences:
http://lists.runrev.com/mailman/listinfo/use-revolution
