On Jun 26, 2005, at 3:52 PM, Nicolas Cueto wrote:
Ok, the problem. A request for data
made to a server stack by stacks via
a LAN will on occassion return empty.
The method you have can create multiple sockets with the same socket
id. This can cause confusion in write, read and close.
For TCP, there is no need to separate the response connection from the
query connection.
You have used variables starting with a t as if they are global, but I
don't see any global declaration. Some people use the t prefix as
meaning local to the handler (strictly, the call of the handler).
I don't see a reason for the 'wait with messages' in the first handler.
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.
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
