The Translation API has a different TOS than the Custom Search and Search APIs. You can cache translations for no more than 15 days.
You will have to figure out how the different, applicable TOS's affect your application. For the record (since I forgot to mention it previously on this thread), I am NOT a legal expert, and if you have any doubts or concerns AT ALL, you should consult someone who is. Jeremy R. Geerdes Generally Cool Guy Des Moines, IA For more information or a project quote: [email protected] If you're in the Des Moines, IA, area, check out Debra Heights Wesleyan Church! On Mar 1, 2011, at 4:59 PM, Zdravko Gligic wrote: > Jeremy, > > What about translations of things like YouTube video title and > description text - where both the translated and the original text are > cached, so that the original text can be compared to what YT currently > has - to ensure that cached translation is never served for outdated > original text ? > > Thanks again, > Zdravko > > On Tue, Mar 1, 2011 at 5:52 PM, Jeremy Geerdes <[email protected]> wrote: >> I don't think so, and here are two reasons why. >> >> 1. The TOS prohibit the making of automated requests. While you could design >> such an application such that the request(s) are made when a user hits the >> page, you would not be able to run a cron job that would automatically >> update your cache. >> >> 2. The TOS also prohibit you from transmitting data obtained from the Custom >> Search API on behalf of one user to any other user. I.e., you can't display >> results received by one user for another. If you're not dealing with the >> Custom Search API, but with News or Image, etc., you can "clip" results and >> store them locally, but it has to be done by an end-user. I.e., you can >> cache the results, but only if someone specifically chooses to do so. >> >> Jeremy R. Geerdes >> Generally Cool Guy >> Des Moines, IA >> >> For more information or a project quote: >> [email protected] >> >> If you're in the Des Moines, IA, area, check out Debra Heights Wesleyan >> Church! >> >> On Mar 1, 2011, at 3:59 PM, Giulia wrote: >> >>> I'm developing Google API products, but I still do not understand >>> some Google's use policies, I want to ask: >>> If I want to assure my pages open speed, I make some keywords as tags >>> (not the user directly type the words) via a API search submit, and >>> then I cache the return results into a database (for a couple of hours >>> update the cache data and delete the old cache datas), whether it is >>> allow? Thanks. >>> >>> -- >>> 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. >>> >> >> -- >> 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. >> >> > > -- > 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. > -- 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.
