I've been following this thread with curiosity.  Given the variety of
ways that the various search engine marketing APIs (so I'm not just
picking on Google here) use to signal an error (500, refused
connections, ignored connections, as well as the ever popular  method
of just sending back some formatted HTML and CSS that says "we too
D**N busy now try again in 15 minutes"), why would  you presume that
200 always means OK?  Just treat 200 as "potentially" OK and then
check to see if it has an error/fault structure in it.  If it doesn't
then you're probably good to go.  If it does, well now you know what
the error is and can do something about it.  I gave up trusting the
exact HTTP responses from these APIs a long time ago - try to imagine
the amount of code behind them on the engine side of things.  There's
always going to be something buggy or just plain "strange" no matter
how hard they try to make them perfect.

my 2 cents!

-- 
You received this message because you are subscribed to the Google Groups 
"AdWords API Forum" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to 
[email protected].
For more options, visit this group at 
http://groups.google.com/group/adwords-api?hl=en.

Reply via email to