> There is a fundamental mismatch here (exactly as with the LastError
> property otherwise discussed on this mailing list), in that the code
> is trying to report multiple *classes* of errors within single
> variables.

This is not true!

First error indicator is result of HttpMethod call.

= true - target server was contacted and got some HTTP reply. But 
this reply can be error message from server too. So, is reasonable to 
check HTTP error code here.

= false - target server cannot be contacted. Here is no reason to 
check HTTP result code, just because we cannot contact them. 
Reasonable is to check sock.LastError (and Sock.ssl.lasterror, if SSL 
was used) for error details.

In case of false result is setted HTTP error code to 'hard fail' 
value 500 too. It made error check very simple in cases when you need 
to know just: "has been OK or not?". However it not break detailed 
error analyse, if you wish. (see before...)


-- 
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 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
synalist-public mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/synalist-public

Reply via email to