Re: AdWords API Why must I blindly poke the cat? - pbac...@cvisiontech.com - com.googlegroups.adwords-api

5 messages in com.googlegroups.adwords-apiRe: AdWords API Why must I blindly po...

From	Sent On	Attachments
pbac...@cvisiontech.com	22 May 2006 09:44
Patrick Chanezon	22 May 2006 10:17
pbac...@cvisiontech.com	22 May 2006 10:55
pbac...@cvisiontech.com	22 May 2006 11:11
Patrick Chanezon	22 May 2006 11:49

Subject:	Re: AdWords API Why must I blindly poke the cat?
From:	pbac...@cvisiontech.com (pbac...@cvisiontech.com)
Date:	05/22/2006 11:11:55 AM
List:	com.googlegroups.adwords-api

Apres avoir vu votre blog, je pense que je devrait vous dire merci pour votre conseille. Mais, ca ne change pas ce que je pense au sujet de l'API. Peut-etre I'll just write some of my own front end to handle the conversions...Mais, heuresement, je recoit une salaire horaire. My french is rusty, please forgive.

Phil

Assuming the mapping of the XML types to language specific types, and vice-versa, is a consistent, non-random function it still seems silly that I'm forced to use different types of data to represent descriptors that represent qualities that are semantically the same. I understand now where to find the information neccessary for determining the types I need to use, but that doesn't change the fact that they're disconcertingly arbitrary.

Patrick Chanezon wrote:

The AdWords API uses WSDL with doc/literal to define the calls it makes available. The types of each parameter is specified in the online documentation http://www.google.com/apis/adwords/developer/index.html Which contains references to the WSDL, where you can find the xml schema type to use. How these xml schema types map to your language types is specifc to the soap toolkit you are using.

On 5/22/06, pbac...@cvisiontech.com <pbac...@cvisiontech.com> wrote:

There must be some love of the uncertainty principle at Google HQ. Any first-timer to devlopment with the Adwords API will likely run into trouble if they are trying to use Python for anything non-trivial. When submitting information for ad groups, campaigns, or anything else, why can't I set up a dict with information as it was delivered to me? Why must I force a 'maxCpc' to be a string so that I can then coerce it to a "SOAPpy.Types.untypedType", even though an 'id' can be sent as an int? They both serve as descriptions of a numerical property. They should accept the same types. Further, why does the API documentation not inform me of what types I must use when submitting information? Some of the neccessary types can be inferred by reading the sample code, but still, not all possible fields and their corresponding neccessary types appear in the sample code for any given language, and having previously written a fair amount of Perl code using the AdWords API, I can say that different languages, even when both are dynamically typed, require different methods of passing these simple parameters. In short, why are all fields of any given AdWords entity (e.g. ad group, campaign, etc.) not represented by either a simple string, or a simple int? Hell, they could all be strings for all I care, all I want is that there might be some consistency and predictability, you know, like maybe this complex scheme: ints for numerical data, strings for textual data?

Argh, Phil

-- Patrick Chanezon, Google API Evangelist http://blog.chanezon.com/ http://www.google.com/apis/adwords/

------=_Part_65416_27574856.1148318287217 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable X-Google-AttachSize: 2637

The AdWords API uses WSDL with doc/literal to define the calls it makes
available. The types of each parameter is specified in the online
documentation <a
href="http://www.google.com/apis/adwords/developer/index.html">http://www.google.com/apis/adwords/developer/index.html </a> Which contains references to the WSDL, where you can find the xml schema
type to use. How these xml schema types map to your language types is specifc
to the soap toolkit you are using. P@ <div> On 5/22/06, <a
href="mailto:pbac...@cvisiontech.com">pbac...@cvisiontech.com</a> <<a
href="mailto:pbac...@cvisiontech.com">pbac...@cvisiontech.com</a>>
wrote:<blockquote class="gmail_quote" style="border-left: 1px solid
rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"> There must be some love of the uncertainty principle at Google HQ.
Any first-timer to devlopment with the Adwords API will likely run
into trouble if they are trying to use Python for anything non-trivial.
When submitting information for ad groups, campaigns, or anything else, why can't
I set up a dict with information as it was delivered to me? Why must I force
a 'maxCpc' to be a string so that I can then coerce it to a "SOAPpy.Types.untypedType", even though an 'id' can be sent as
an int? They both serve as descriptions of a numerical property.
They should accept the same types. Further, why does the API
documentation not inform me of what types I must use when submitting information? Some of
the neccessary types can be inferred by reading the sample code, but still,
not all possible fields and their corresponding neccessary types appear in
the sample code for any given language, and having previously written a fair amount of Perl code using the
AdWords API, I can say that different languages, even when both are
dynamically typed, require different methods of passing these simple
parameters. In short, why are all fields of any given AdWords entity (e.g. ad
group, campaign, etc.) not represented by either a simple string, or a
simple int? Hell, they could all be strings for all I care, all I want is
that there might be some consistency and predictability, you know, like maybe
this complex scheme: ints for numerical data, strings for
textual data? Argh, Phil http://blog.chanezon.com/</a> <a
href="http://www.google.com/apis/adwords/">http://www.google.com/apis/adwords/</a>

------=_Part_65416_27574856.1148318287217--