>however with socks "#20xxx is not a winsock error"
>is displayed everywhere with socks errors
What's the problem? ICS uses custom WSocketErrorDesc anyway so just add a
definition of socks errors there.
--
Anton
--
To unsubscribe or change your settings for TWSocket mailing list
please goto http
Hello,
I'm using TSWocket and have the following problem:
One client and one server running on the same PC (localhost, 127.0.0.1)
use the socket as medium to transport commands.
It normally works as it should but under certain conditions it fails
like this: my application has to deal with Blueto
Anton S. wrote:
>> however with socks "#20xxx is not a winsock error"
>> is displayed everywhere with socks errors
> What's the problem? ICS uses custom WSocketErrorDesc anyway so just
> add a definition of socks errors there.
There should be multiple new functions to lookup error messages IMO.
On
Hi,
1) Command Open succeeds.
2) After the server received command User it closes the connection (FIN/ACK).
3) OnSessionClosed triggers with ErrCode 0.
4) OnRequestDone triggers with ErrCode 0 and the status code from previous
request.
Would you agree that is a bug?
--
Arno Garrels
--
To un