We've been experimenting with using pthreads in php (see pthreads.org) in order to make a multi-threaded application for fast retrieval of TargetingIdeaService data and we've run into a bit of a snag. Any member of a thread must support serialization and since the client library uses the built in php SOAP objects, which cannot be serialized, we can't make the adwords user (or selector or anything else) a member of the thread.
The work around is to just put the whole adwords process in a function in the thread but I'm worried about the overheard of loading the service and retrieving the wsdl for each API call. Is there any way to force the client library to use a locally cached copy of the wsdl to reduce the network overhead? For now we're going old-school with XML and curl, which works fine, but I'd like to go back to using the client library if possible-- it'd save a lot of maintenance hours. -- -- =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~ 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
