Slashdot Log In
Google to Offer API
Posted by
CmdrTaco
on Sat Apr 06, 2002 12:54 PM
from the now-thats-smooth dept.
from the now-thats-smooth dept.
philipx writes "From the ruby-talk archives here's a little interesting snippet from a post you have to check out:
"Here at Google, we're about to start offering an API to our
search-engine, so that people can programmatically use Google through
a clean and clearly defined interface, rather than have to resort to
parsing HTML." It goes on talking about SOAP and I think this is utterly cool."
This discussion has been archived.
No new comments can be posted.
The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
Cool, but.... (Score:4, Insightful)
Re:Cool, but.... (Score:2, Informative)
Re:Cool, but.... (Score:2, Interesting)
Re:Cool, but.... They never said if was free! (Score:3, Insightful)
I just wonder how it will tie into my app. Will it open my browser? Will the Google Bar plugin be the foundation?
We'll just have to wait and see...
Re:Cool, but.... They never said if was free! (Score:4, Informative)
I just wonder how it will tie into my app. Will it open my browser? Will the Google Bar plugin be the foundation?
The post describes a SOAP web service which in most cases is an RPC call in your application of choice. However unlike RPC in days of yore using SOAP to do RPC in applications is relatively easy. If you want to learn more about SOAP I suggest reading A GEntle Introduction To SOAP [weblogs.com] by Sam Ruby for an overview of the protocol and A Busy Developer's Guide to WSDL 1.1 [weblogs.com] to see how one could go from defining a WSDL file (as the Google sys admin is trying to do) to actually accessing the web service remotely from a Java application.
There is also a grab bag of resources on XML webservices [gotdotnet.com] at the
To answer your question, if the Google API is available as a web service then it can be intergrated into any application at all from command line to dynamic web page to GUI application as long as there is network availability on the host machine.
Parent
Barter worked for a long time... (Score:3, Insightful)
Google benefits from the monetery system in an obvious way. They also benefit from the barter system by vastly adding to the crunch power which hopefully improves their indexing/grading system. Unused clock cycles which would otherwise be wasted can now earn some value for the users and at the same time give google the 'value' for providing their service.
So their 'open' system if presented in the form of barter could actually work for the advantage of both parties involved.
Re:Cool, but.... (Score:2)
That's the beautiful thing about a site that doesn't fund themselves through the use of banner ads. It doesn't MATTER if you access their content through the main website, an affiliate like yahoo, or an api interface.
They sells text ads on their main site. Yahoo pays them a fee. So how will the API users pay for themselves?
Re:Cool, but.... (Score:3, Informative)
- Amit
Cool feature (Score:4, Insightful)
Google topic icon (Score:3, Funny)
Re:Cool feature GREAT IDEA! (Score:2, Insightful)
all of us do nothing but rave about google day and night
for it is a search engine we love, with a company many of us have come to love
I for one would love to see google have its own slashdot icon
Come to think of it, there are plenty of USELESS icons none of us give a damn about
the following are a few:
Heres hoping for a new google icon!!
Just my two cents, all taxes included
Sunny Dubey
DoS Google? (Score:3, Interesting)
With the exposed API I could see, by malice or sheer accident, floods of queries coming in...
Re:DoS Google? (Score:4, Informative)
In fact, an attack through the front door will be more likely to succeed because you're hitting the rendering engine, which takes a lot more CPU time (believe it or not) than the search engine.
OTOH the back door is lightweight and is as such advantageous for not only third parties but also Google itself to employ.
Besides, if you're being abused, if you don't want to use technological avenues to keep miscreants away, you can always use legal ones.
Parent
This is great. (Score:2, Interesting)
Re:This is great. (Score:2)
Ah, but they do [slashdot.org]
Re:This is great. (Score:2, Interesting)
Re:This is great. (Score:2)
Re:This is great. (Score:3, Insightful)
Text ads... Open standards for content distribution... If only certain other sites would follow...
Apples and oranges... Google's bread and butter is their patented PageRank technology, which they license for what I'm sure is a lot of money. Slashdot, having made the decision to opensource slashcode do not have this option, therefore we're forced to endure banner ads and subscriptions as their only source of revenue. Ironic, eh? The people that screamed so loud about how long it took ./ to release the source for slash are now bitching about subscriptions and banner ads.. Like it or not, if slashcode was proprietary it could be sold and licensed and you wouldn't have to see ads here (or at least not the larger ones). Sourceforge figured this out too late, and are now trying to sell the SourceForge software as a source of income.
Hopefully ./ will wise up and figure out if they ever want to make any real money they'll have to offer a real service.. Like consulting to companies/webmasters to setup slashcode for customers (like MySQL AB does)... Too bad VA Linux went out of the hardware market. I think a pre-configured "Slash Appliance" (sort of like google's Search Appliance [google.com]) would be cool as hell for companies needing an internal collaboration system. ./ has really missed the boat here, IMHO.
Shayne
This is the beginning of the revolution (Score:5, Insightful)
They'll need a business model of some sort -- without the ads, and with the potential this has to hammer their servers, they'll need to meter access to the API in some way. But I'll pay -- where do I sign up?
I'll bet that this is how they'll end up making most of their money a couple of years from now.
Re:This is the beginning of the revolution (Score:3, Interesting)
I'm curious as to whether people would actually want such functionality from MSDN. It's one thing to be able to do a Google search from a function call and get the results back as XML but do people want API docs and technical articles retrieved via getArticle() and getAPI() webmethods?
One place where it might be useful however is KnowledgeBase articles [microsoft.com]. Perhaps a web service that retrieves a KB article given the Q number (e.g. Q123456) might be useful.
Disclaimer: This post is my opinion on doesnot reflect the thoughts, strategies, intentions or opinions of my employer.
Re:This is the beginning of the revolution (Score:2)
Re:This is the beginning of the revolution (Score:2)
Another option is to give better access to paying customers: a paying customer is given unlimited use of the search, while private individuals (distinguished via IP/registration/...) would be limited to, say, one search per 5 seconds. It would be great to be able to use this API for some small things without having the hassle of paying. A 5-10 second delay isn't very bad in a small home situation, but is out of the question for any larger-scale applications.
I'd say it would also be consistent with their current user-friendly business model, and give another jolt of good PR for them.
Cool! (Score:2, Insightful)
Could this be in response to the supposed competition from tokohma? open up thier results in some way to increase thier usage?
Contradicts the terms of use (Score:4, Interesting)
So how useful might that API be if you can't do anything with it...
Re:Contradicts the terms of use (Score:5, Interesting)
I'd assume that the API would be subject to a different set of terms and conditions than those for the main site. Given that it'll probably be a pay-for-use service (as another poster hinted at), it'd most certainly be that way.
Parent
Re:Contradicts the terms of use (Score:3, Informative)
Re:Contradicts the terms of use (Score:2)
I suspect that, despite the outcry and outrage from some quarters, they're not simply going to give away their entire search engine API connected to their search farm. Perhaps they'll limit it, meter it, and even charge for it. All would be more then fair.
No contradiction (Score:5, Insightful)
On the other hand, Google would obviously not want you to set up your own search site that passes queries to their engine, harvests the results, and presents them on your own site. That is the obvious target of the "Personal Use" restriction.
As for the "Automated Query" restriction -- well, what do you think they mean by "Automated"? Programmatic access to their engine? They couldn't prevent that even if they wanted to. "Automated" obviously means programs that issue hundreds of queries for data mining purpose. Example: crawling the Groups archives to harvest email addresses.
(This was a matter of some concern to me, when I noticed that the Google Usenet archives included all my company's private groups. I'd innocently used by real corporate email, innocently thinking that the groups weren't accessible outside the company. But the spam volume is still very low. Their bot detection software must be quite good.)
Note that making a simple API available doesn't enable any new kind of access to the Google engine. A clever programmer can already parse the HTML results. The API just makes it easier -- and gives Google another product they can sell licenses for.
Parent
Re:No contradiction (Score:2)
This sounds cool, but.. (Score:2, Insightful)
Ok, it can be done already, but this would make it possibly too easy...?
Also, this will miss out their ads etc that they get revenue from, I wonder what their long term stratagy is?
Re:This sounds cool, but.. (Score:2)
Or lets say Google spikes the search request at some competitors to prove they are using Google.
So sure they could do it, but I doubt any popular site could get away with it for long.
Re:This sounds cool, but.. (Score:2)
Some unscrupulous players could surely abuse this by 'making their own' search engines that essentially rip off google without any hassle what so ever?
Yahoo [yahoo.com] hasn't had enough problems with it to take it down. It's really nice being able to make my own PHP script to display customized stock quotes on my PDA.
Actually, it works quite OK. (Score:3, Interesting)
If you run the Ruby script, as is, the result is thus:
#: Exception from service object: Invalid authorization key: xxxxxxxxxxxxxxx (SOAP::FaultError)
If somebody starts abusing a particular key, it's a no-brainer for Google to shut the key off.
The app I'm working on could use this (Score:2)
Explanation / Keep Supporting Google (Score:3, Interesting)
---
The following is the preliminary code that a particular Google sysadmin (ian@) is trying out. He'd prefer to have a single WSDL file do all of the configure (from Google's end to client), but he first needs to get some advice from an experienced Ruby hacker.
Also, let's keep in mind that this API will actually be decreasing Google pageviews and hits, which will in turn make their AdWords, AdWordsSelect, and textads less effective. So, it's our duty to continue to support Google and show them that the free/open source software people are behind them 100%. We know that Teoma just doesn't deliver, and Google's already got 3 billion pages indexed and cached.
Support Google today, because they're the future of information indexing on the Web!
--- begin code ---
#!/usr/bin/ruby
require 'soap/driver'
endpoint = 'http://api-ab.google.com/search/beta2'
ns = 'urn:GoogleSearch'
key = 'xxxxxxxxxxxxxxx'
service = 'file:GoogleSearch.wsdl'
query = ARGV.shift || 'foo'
soap = SOAP::Driver.new(nil, nil, ns, endpoint)
# uncomment the next line to dump the traffic on the wire
#
#soap.setWireDumpDev(STDERR)
soap.addMethodWithSOAPAction('doGoogleSearch', ns, 'key', 'q', 'start',
'maxResults', 'filter', 'restrict',
'safeSearch', 'lr', 'ie', 'oe')
r = soap.doGoogleSearch(key, query, 0, 10, false, nil, false, nil,
'latin1', 'latin1')
printf "Estimated number of results is %d.\n", r.estimatedTotalResultsCount
printf "Your query took %6f seconds.\n", r.searchTime
Is this a subscription service? (Score:4, Interesting)
I havent tried to get it to work yet, due to not having ruby installed, but does this imply some sort of subscription service?
Possibly a new way for them to raise revenue? Im assuming that the bold line means the authors key has been blanked out so other people cant abuse this service for free?
Lameness filter encountered. Post aborted! Reason: Too much repetition. :/
OpenGoogle? (Score:2, Funny)
We can finally find out how to implement their PigeonRank system...
Good to see this idea return (Score:4, Interesting)
Of course, now it's just forbidden. I am surprised they would go back to such a service, it would seem to wind up losing revenue for them depending upon whether or not people are good about passing along whatever Ad-words Google returns. They could expect the traffic to be low enough to not matter compared to the continued word-of-mouth benefit. Or access to the SOAP interface could be offered as a subscription model (pure speculation on my part).
-Robert
Re:Good to see this idea return (Score:2)
If the results are returned using SOAP, then the backend surely would want to display the ads because a lot of the time, they are what the user is looking for.
I know if I am looking to buy something search Google for vendors, I am more likely to choose a vendor from the Ads on the side. I figure it is a bit safer since these people actually have something invested in it.
The only reason I can think that someone would filter out the ads is simply because they want to hurt Google. Who wants to hurt Google though?
The click through rate is probably going to make things hard since there is no way to tell if a user clicked an ad. That just means a different guage...
Ode to Google :) (Score:4, Insightful)
They have always made the right decision ! they have offered internet users an incredible asset ! and I was so much grateful when they decided to rescue Deja, a site something I just don't know how I can leave without !
I view them as the most "honest and fair" site on the Net ! and without any doubt the most useful too.
Go Google ! you are showing the right way ! to all these stupid-crapy-portal sites which have invaded the net, I just hope you manage to stay in business and prosper for a loooooong, looooong time
wow -- wish i'd had this earlier (Score:2)
what about the law suit (Score:2)
Not publically accessible (Score:2)
at com.google.soap.search.QueryLimits.lookUpAndLoadF
...
Alas, looks like the rest of us won't be able
to play with Google's beta SOAP service. Which makes quite a bit of sense - this would be a great way for Google to allow people to resell Google in a standardized way, be it from inside a program (scary, too easy to reverse engineer) or from some other web service (less scary.
These guys drive me crazy. (Score:5, Funny)
Already something like this... (Score:3, Informative)
http://www.google.com/search?hl=en&q=blah&outpu
with
http://www.google.com/search?hl=en&q=blah&outpu
with
http://www.google.com/search
-nonymous
API for Biz Partners ($$$) Only ??? (Score:3, Informative)
http://www.google.com/xml?q=slashdot [google.com]
You'll (probably) get an error page.
I read about this on Scripting News [scripting.com] in February:
Dave Winer made an inquiry [userland.com] to Google about accessing this XML API.
Their initial response [weblogs.com] was not very helpful, asking for the link to be removed, and saying that the link is "obviously reserved for Google partners." Eventually, Google let Dave access the API. Now, he sounds like he's under NDA [userland.com] about this.
Slash could use this. (Score:4, Insightful)
Need to reference John Carmack's comments? Sorting him out of the masses is next to impossible. Even a comment poster as prolific as Signal 11 (arguabley slashdots first and greatest Karma Whore) is nearly impossible to find. First 30 matches of how many? You want to sort through jeffy124's 700+ comments and 24 submitted stories just to find the pertinate one I need by hand? Not to mention the benefit to Slashdot's editors, being able to follow a clear history of articles on a given subject to look for repeats and make more informed editorial commentary. If 90% of readers never read the comments, the editors owe that 90% the sort of editorial commentary attached to each story that only good research can provide.
In fact, the editors could try it on an interim basis immediately, and provide the service to readers only if they had the resources. I sort of get the feeling that the editors are still thinking of slashdot as a small time blog run out of their apartment closet server.
Run google on slashdot now and you get the news from three weeks ago. Incorperate a google box or google APIs into Slash so I could search today's news and I would Pay 10 cents of subscription funds per search in a heartbeat.
Editors: look at the number of hits to your current broken search engine. Double that number because a dedicated google box would be so much better it would get used a whole lot more. Multiply that by 10 cents per search. See if the numbers work to afford the initial expenditure to get a nice yellow rack mount google box. Slashdot is sitting on a goldmine of data and no one can search it and Slashdot cannot profit from it without a nice pay per search subscription using the best engine available.
Re:Since when do we like Google? (Score:3, Funny)
We like them Monday, Wednesday, and Friday.
We love them Tuesday, Thursday, and Saturday.
And we alternate Sundays.
Get with the program.
Re:Ron Hubbard's role in this (Score:2)
Re:Pay-per-placement will pay for this... (Score:2, Informative)
That was the very thing that turned people onto Google. I very much doubt that they would change that.