On Fri, Mar 19, 2010 at 01:59:08PM -0700, AdWords API Advisor wrote: > Hi John, > > Thanks for the great feedback, and for offering to help move this > project forward. Having the Perl and AdWords communities working > together would be great and we're open to the possibilities it can > bring. > > We would appreciate it if you could get us in touch with the > maintainers of SOAP::WSDL module.
The SOAP::WSDL module is maintained on sourceforge. The author, Martin Kutter, can be reached at [email protected] [CC'd] The development mailing list is also on sourceforge. The archive is at: http://sourceforge.net/mailarchive/forum.php?forum_name=soap-wsdl-devel You can subscribe via http://sourceforge.net/mail/?group_id=111978 > It would be great to talk in detail about the patches and how those > changes can be worked into the core library. I've recently raised the issue of better support for AdWords with Martin. See "Current Status? (especially re support for Google Adwords)" in the archives.) I believe he's keen to see the situation improved. He's recently made a development test release to CPAN http://search.cpan.org/~mkutter/SOAP-WSDL-2.00.99_1/ which has shown up a range of problems in automated testing: http://matrix.cpantesters.org/?dist=SOAP-WSDL+2.00.99_1 > In regards to the AdWords library on CPAN, we agree that the old > library is deprecated and should be marked as such. To help with that I added a review a while ago to point out it wasn't being updated and to direct people to the new API: http://cpanratings.perl.org/dist/Google-Adwords Rohan [CC'd] would you consider deleting your all your Google-Adwords distributions from CPAN? They'll still all be available via BACKPAN (http://backpan.perl.org/authors/id/R/RO/ROHAN/) but deleting them will mean Google-Adwords will no longer be indexed or appear on search.cpan.org. That'll reduce the current confusion. FYI You can delete the files at https://pause.perl.org/pause/authenquery?ACTION=delete_files > Putting the new library on CPAN would be great for developers, Not just for developers but for yourselves as authors. The automated testing you get via cpantesters (see above) is invaluable. > but what's held us back > from doing that in the past is that the installation is currently very > manual, involving the SOAP::WSDL patches, etc. We can work on > eliminating these steps so that distribution of the library is > simpler. > > Thanks again for the interest and excitement. We look forward to > working with you and other Perl developers. Since Martin's time is limited and he's very open to contributors (see http://cpansearch.perl.org/src/MKUTTER/SOAP-WSDL-2.00.99_1/HACKING) perhaps one of the adwords developers could spare some time to contribute directly to the project and commit changes to the repository. Now would be a great time as Martin's working towards a major release based on the Typemap branch that AdWords API uses. Tim. > Best, > - Eric Koleda, AdWords API Team > > On Mar 18, 9:57 am, john napiorkowski <[email protected]> wrote: > > > > I think some things I'd like to help work out would include: > > > > 1) SOAP::WSDL patches, if these are good patches I will contact the > > cpan author and see if we can get them integrated and released on > > CPAN. CPAN is the standard toolchain for perl developers and is the > > community approved method for contributing code. So if these changes > > are needed I'd like to get them on CPAN. Please consider if this can > > work with your legal team and terms. We' d be happy to add a note to > > the author section saying something like, "some code contributed by > > Google" or similar. Let me know what you think > > > > 2) Ideally this code in google-api-adwords would also get released to > > CPAN in a regular way. obviously the developer repo and related tools > > like bugtracking and discussion can reside anywhere, but again any > > Perl developer would look to CPAN first for code. If the existing > > Google::Adwords module is going be be considered deprecated I need to > > get the author to mark a new release as such, and ideally we'd cut a > > working version of the code in the repository over here onto CPAN, > > like under Google::API::Adwords or similar. Is there someone on the > > Google end that wants to own this CPAN module? If you need help > > getting this together I would gladly assist. > > > > Myself I am not a SOAP expert. In general SOAP is not preferred by > > any dynamic language, it is a better fit for strongly typed languages > > such as Java. So I can't assist very much on that side. However I > > can act to help facilitate communication between our communities and > > with other bookekeeping tasks, like CPAN access, etc. Some developers > > on our side may be willing to put some additional time into getting > > all this working. > > > > Thanks! > > > > John Napiorkowski > > > > > 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 To unsubscribe from this group, send email to adwords-api+unsubscribegooglegroups.com or reply to this email with the words "REMOVE ME" as the subject.
