I have just read that there are YET MORE changes to a production API:
http://googleadsdeveloper.blogspot.com.au/2012/03/specifying-version-when-requesting.html

The page:
http://code.google.com/apis/adwords/docs/guides/reporting.html

 ... has been quietly updated with the new namespace requirement in the 
report definition, which was MOST CERTAINLY NOT THERE when I copied and 
pasted the template into our code.

Recent last-minute, badly planned and apparently untested hacks to 
production APIs have caused many people many issues. The report service not 
returning paused ads comes to mind. So why do you keep hacking the ONLY 
AVAILABLE version? Can't these changes wait for the next API version? Maybe 
you should test your own API before releasing it and removing all other API 
versions? What is the point in even having a version number if you keep 
hacking how it behaves each day anyway?

I should note that the last message I posted on this topic triggered a 
FLOOD of private emails by other developers saying "we feel your pain, but 
are too scared to say so in that tone in the forums".

-- 
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
Also find us on our blog and discussion group:
http://adwordsapi.blogspot.com
http://groups.google.com/group/adwords-api
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~

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

Reply via email to