لطفا منتظر باشید ...
Hacks 92-100
When search engines first appeared on the scene, they were more open to being spidered, scraped, and aggregated.
Sites like Excite and AltaVista
didn't worry too much about the odd surfer using
Perl to grab a slice of a page or meta-search engines including their
results in aggregated search results. Sure, egregious data suckers
might get shut out, but the search engines weren't
worried about sharing their information on a smaller scale.Google never took that stance. Instead, they have regularly
prohibited meta-search engines from using their content without a
license, and they try their best to block unidentified web agents
like Perl's LWP::Simple module
or even wget on the command line. Google has even
been known to block IP address ranges for running automated queries.Google had every right to do this; after all, it was their search
technology, database, and computer power. Unfortunately, however,
these policies meant that casual researchers and Google nuts, like
you and I, didn't have the ability to play with
their rich dataset in any automated way.Google changed all that with the release of the
Google Web API (http://api.google.com/) in the spring of
2002. The Google Web API doesn't allow you to do
every kind of search possiblefor example, it
doesn't support the
phonebook:syntaxbut it does make
available Google's eight-billion-page web database
so that developers can create their own interfaces and use Google
search results to their liking.
|
key , a login of sorts to the Google API. Each key affords
its owner 1,000 Google Web API queries per day, after which
you're out of luck until the next day. Even if you
don't plan on writing any applications, having a key
at your disposal is still useful. There are various third-party
applications built on the Google API that you might want to visit and
try out; some of these ask that you use your own key and allotted
1,000 queries.
