Re: GoogleAPI class

Sebastian Bergmann wrote:

Shane Caraveo wrote:

And I may well end up requesting it get removed.

Which I can understand. It seems I got a bit too excited about this :/

Yep, I was just as excited to see the first two PHP google wrappers using PEAR SOAP! :)

I DO NOT want to start adding hundreds of soap services at the top level of heirarchy in PEAR, and I by far prefer they NOT be in the SOAP namespace.

Point taken. So, where to put it now? Creating a WebServices_* 'Namespace' sounds reasonable, I guess. On the other hand, so does Search_*.

I just want to have some thought and discussion on it, and have an agreement about how best to handle it, or if we even should handle it via pear (see my other email). As a note on the WebServices namespace, I'm hesitant to use it because there is one very usefull feature I would like to use it for...a generalized wrapper around SOAP, XML-RPC, and any other protocol like that, kind of like the DB classes. Shane