NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.
All the Perl that's Practical to Extract and Report
Google SOAP!
More |
Login
| Reply
The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
several minutes ago. We don't need no stinkin' tactical nukes.
(By the way, do you have change for 10 million people?) --lwall
Stories, comments, journals, and other submissions on use Perl; are Copyright 1998-2006, their respective owners.
I can't stand it. (Score:2)
What was wrong with Google's lovely simple XML interface, where you simply replaced the word "search" for "xml" in the querystring, and got nice XML back detailing everything such a SOAP response would? (you can no longer do this without paying for the service, but I believe it's still there) Do we really need the SOAP layer on top of this? Is plain HTTP and a smattering of XML really that much harder than an API?
I feel like such an old fart when I see things like this and it just looks so "new for the sake of it"...
Reply to This
Re:I can't stand it. (Score:1)
Re:I can't stand it. (Score:3, Interesting)
When you said that, I first thought you were referring to this lovely bit of API:
soap.addMethodWithSOAPAction('doGoogleSearch', ns, 'key', 'q', 'start',
'maxResults', 'filter', 'restrict',
'safeSearch', 'lr', 'ie', 'oe')
r = soap.doGoogleSearch(key, query,
--
Esli epei eto cumprenan, shris soa Sfaha.
Aettot ibrec epesecoth, spakhea scrifeteis.
Re:I can't stand it. (Score:1)
I think that first part of the incantation is priming the Ruby SOAP interface, not part of the google interface itself. And the arguments to the second were what was named in the first call (some sort of key, the query itself, start at result 0, return 10 results, don't filter results, no clue :), adult search filter off, no clue, input encoding, output encoding).