Re: [twsocket] Socket not sending SYN ACK - Help?

Thanks for your replies: 1) Yeah I know the SYN SYN ACK ACK should establish the connection and agree the SYN SYN ACK RST ACK looks like a client problem but the same client works to another machine. I'll try intercepting the packets too and see if that reveals

[twsocket] Help on ICS's HTTP client component

Hello everyone. Note: This is a re-post of a message sent to the Talk list, with more detail on the problem. This message gets sent the second time to this list too. I sent the first one before receiving elist's subscription confirmation so I don't think it went through. I'm having some

Re: [twsocket] Help on ICS's HTTP client component

I did implement a kind of time-out mechanism into my download thing: if no event is triggered for a given amount (no state change, no data received, no error) I consider the connection to be timed out. This gets my application back on the track working properly but this feels like a hack, it

Re: [twsocket] Receive() returns -1

Hello, Sorry mixed it up with with a 0 result 0 means a closed connection, -1 means an error, check LastError. Correct that it is an error, but no need to check LastError. TWSocket take care of the error if it happens here. Just Exit OnDataAvailable when Receive returns = 0. --- Rgds,

Re: [twsocket] Receive() returns -1

Hello Jack, I have a TCP socket client. In some cases, OnDataReceived() gets fired for multiple times with ErrCode = 0 I never have seen a winsock error in OnDataAvailable. You can ignore the check in that event safely. Receive() the return value is always -1 so the application can not read

Re: [twsocket] Receive() returns -1

Wilfried Mestdagh wrote: Sorry mixed it up with with a 0 result 0 means a closed connection, -1 means an error, check LastError. Correct that it is an error, but no need to check LastError. TWSocket take care of the error if it happens here. Just Exit OnDataAvailable when Receive returns =