So how should I handle connection errors in a way that makes user aware of
error AND not cause any kind of disaster? Catch the error code in
OnSessionConnected
Yes, indeed.
and (using some kind of PostMessage) display actual error
message outside OnSessionConnected?
If you like it so, no pro
Hello!
>>> 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
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 chec
Hello!
> 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
> -Oorspronkelijk bericht-
> Van: twsocket-boun...@elists.org [mailto:twsocket-boun...@elists.org]
> Namens Piotr Dalek
> Verzonden: dinsdag 3 mei 2011 11:22
> Aan: TWSocket
> Onderwerp: [twsocket] Connected when not connected
>
> Hello.
>
> In WSocket's
Hello.
In WSocket's DO_FD_CONNECT procedure, the socket state is set to wsConnected
even if the socket has failed to connect (for example, on 10061 error), then
the SessionConnected handler is called and after that, check for actual
error is performed, where socket is closed when error is not zero
