I knew that something happened when users start to complain few days
ago :-)

Just to be sure, I'm using the languageDetection API to detect (and
validate) the language of Word documents: to do so I'm extracting the
text and send several requests (using Flex/Flash) to the API and
compute the result. Using Firebug, I can see that now my requests are
blocked for a certain amount of time (from few ms to several seconds!)
before being "released". So I added an API key today to get around
this problem. Is it the correct way or am I missing something?

Thanks in advance,
Cyril

On Jan 19, 10:24 pm, Adam Feldman <[email protected]> wrote:
> Over the last several years, you've helped make Google's AJAX APIs
> incredibly successful.  Not surprisingly, however, there are some
> people who try to take advantage of these free APIs by using them in
> ways that they were not designed for, abuse which is prohibited by the
> Terms of Use (http://code.google.com/apis/ajaxsearch/terms.html).
> Specifically, some servers are making countless requests - requests
> not made on the behalf of an end-user - in an attempt to scrape data
> from the API.
>
> To help us discourage this behavior without impacting legitimate
> developers, we're adding a new parameter to the RESTful interface,
> userip.  With this parameter, developers have the option of supplying
> the IP address of the end-user on whose behalf they are making the API
> request.  Doing so will help us distinguish this legitimate server-
> side traffic from the more abusive scraping in which there are no end-
> users.
>
> Use of this new parameter is *not* required.  However, if it is not
> included with server-side requests, those requests are more likely to
> be interpreted and automatically blocked as abuse, especially in
> situations where a server is sending a high volume of traffic to the
> API.  Additional safeguards you can take include setting setting a
> valid HTTP referer (as required by our Terms of Use) and using an API
> key (http://code.google.com/apis/ajaxsearch/signup.html).  These
> additional measures will help us contact you in case there are
> problems with your website or application (sometimes a programming
> error results in massive traffic, forcing us to block your access if
> we are unable to contact you).  In choosing to utilize this parameter,
> please be sure that you're in compliance with any local laws,
> including any laws relating to disclosure of personal information
> being sent.
>
> Check the documentation for usage of the new 
> parameter:http://code.google.com/apis/ajaxsearch/documentation/reference.html#_...
>
> And don't hesitate to send us your feedback in this group.
>
> Thanks,
> Adam Feldman
> Product Manager
> Google Developer Team

-- 
You received this message because you are subscribed to the Google Groups 
"Google AJAX APIs" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to 
[email protected].
For more options, visit this group at 
http://groups.google.com/group/google-ajax-search-api?hl=en.

Reply via email to