> On a separate note; since the socket is closed automatically, the > LastError-variable gets reset to 0 before returning. Would there have > been a way to see the socket errorcode (that was in the variable > before the socket was closed/finalized/whatever) *after* the failed > connection attempt? It would've propably given at least some way to > further debug the situation at the code - or at least give us the > chance to say to the user something like "Sorry, request has failed. > Reason was the cryptical socket error '10054: Connection was reset', > for which we honestly can do nothing about.".
It is similar like problems presented by Willy here. Major problem is about TCP socket closing. It am trying to do gracefull TCP socket closing what overwritint socket error status. I have fixed it now: gracefull TCP closing is done only if socket is in non-error state. Additionally, THttpSend class hide socket error "connection reset by peer" in case of 'unknown' data transfer, where end of transfer is identified by socket close on server. So, this error is legal end of operation in this case. -- Lukas Gebauer. E-mail: [EMAIL PROTECTED] http://synapse.ararat.cz/ - Ararat Synapse - TCP/IP Lib. ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ synalist-public mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/synalist-public
