> The library's author, Lukas, states his case and expected usage in the > following mailing list message (that you're supposed to only > consider/inspect result codes if and only if you got a valid return (true) > from the HttpMethod call):
I had forgotten to mention that Lukas himself points out EXACTLY the same usage scenario that you seem to be evaluating, and the one I was responding to back then, on this page: http://www.mail-archive.com/[email protected]/msg01765.h tml 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...) It is JUST EXACTLY that scenario where you would NOT be checking the HttpMethod() return value, and would NOT want the possibility of a valid HTTP result code indicating a possible _valid_ HTTP error, where any number of other things (non-HTTP..., missing SSL library, ... ... ...) could have triggered it. And where that would be made obvious by the use of a code (or set of codes, possibly all negative) like 900, 999, 0, -1, ... ------------------------------------------------------------------------------ Download Intel® Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev _______________________________________________ synalist-public mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/synalist-public
