Hi All, To help you get started using and updating the client library, we've made sure that the current code is up to date with most of the services from v200909 of the API.
The only services that are missing from this build are InfoService, BulkMutateJobService, and TargetingIdeaService. These services require further patches to the SOAP module in order to support multiple namespaces. For example, some of the obejcts in the InfoService are shared with cm/ and thus defined with https://adwords.google.com/api/adwords/cm/ namespace, others are unique to this service and are defined under https://adwords.google.com/api/adwords/info/ namespace. We hope to implement these patches with your help. The latest version of the code can be found at: http://code.google.com/p/google-api-adwords-perl/. Note that the client library requires patched version of the SOAP::WSDL module, thus make sure to follow instructions in the README file: http://code.google.com/p/google-api-adwords-perl/source/browse/trunk/README Best, - Eric Koleda, AdWords API Team On Mar 17, 10:48 am, john napiorkowski <[email protected]> wrote: > On Mar 16, 6:24 pm, AdWords API Advisor <[email protected]> > wrote: > > > > > > > Hi Rick > > > We are aware that the Perl client library is out of date, and we are > > actively working on updating it to take full advantage of the v200909 > > version of the API. We encourage AdWords API Perl developers to > > contribute to the open source project and help to accelerate the > > process, but we want you to understand that this work will not be > > completed prior to the April 22 sunset of most v13 services. We > > recommend that developers either migrate their applications to another > > language and client library (such as PHP, Python, etc.) or continue > > the development of their own implementation in Perl. A complete list > > of the AdWords API client libraries is available here: > > > http://code.google.com/apis/adwords/docs/clients.html > > > Best, > > - Eric Koleda, AdWords API Team > > Recently blogged about this decision over > at:http://jjnapiorkowski.vox.com/library/post/google-do-no-evil-to-perl.... > > I hope we can work together to address this problem. I really don't > think "use a language other then Perl or write your own bindings" is a > very productive solution. I hope we can do better. > > > > > > > On Mar 8, 1:50 pm, Rick <[email protected]> wrote: > > > > We've been using the perl api for v13, and are trying to use the v2009 > > > api. > > > > However, the perl api appears broken, and we're just not getting any > > > response from google about when, or even if, it will be fixed. > > > > What will happen on April 22, then? Will the v13 calls be turned off, > > > in spite of the fact that the v2009 api is broken? > > > > If google is not going to actually support perl, is there any > > > consensus on what api they actually support best so we can migrate to > > > that language? > > > > Rick -- =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~ Have you migrated to v200909 yet? The v13 sunset is on April 22, 2010. 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 [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
