This is how winsock works. OnSessionConnected is fired with an error,
after it OnSessionClosed is fired with or without an error.
So having TWSocket's state different from actual state should be
normal? If so, then I understand that checking for component state is NOT
enough to check whether it is actually connected or not?
Well, you should probably consider you are connected with error. The error
code being available thru the OnSessionConnected event.
The author of the freeware multi-tier middleware MidWare
The author of the freeware Internet Component Suite (ICS)
To unsubscribe or change your settings for TWSocket mailing list
please goto http://lists.elists.org/cgi-bin/mailman/listinfo/twsocket
Visit our website at http://www.overbyte.be