> Hi,

> 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 considered
normal? If so, then I understand that checking for component state is NOT
enough to check whether it is actually connected or not?

Piotr Dałek

Zapytaj wrozke!
Sprawdz >> http://linkint.pl/f29a2

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

Reply via email to