"One thing you will need to consider is that the Translate API v2 limits you to 100K characters translated per day."
That is very good info to know, thanks. I didn't know they did that. V1 will probably work fine for what I'm doing for the interim. I should consider some option that translates once, then serves the translated version from my server via a client-side request. I will probably have to get Akamai on the phone at some point too. Good call. Thanks again. On May 25, 3:49 pm, Jeremy Geerdes <jrgeer...@gmail.com> wrote: > I would contact Akamai about that, but I can't imagine that their service > would work that way. > > As for running the Translation API client-side, one thing you will need to > consider is that the Translate API v2 limits you to 100K characters > translated per day. That is per API key, so it would not be a great idea to > translate the same thing over and over again on the server-side. If you use > the Translate API v1, there is no hard limit, really, but they have been > clamping down on the throttling. And there is always the looming notion that > v2 should succeed v1 at some point. > > Jeremy R. Geerdes > Generally Cool Guy > Des Moines, IA > > For more information or a project quote: > jrgeer...@gmail.com > > If you're in the Des Moines, IA, area, check out Debra Heights Wesleyan > Church! > > On May 25, 2011, at 5:40 PM, UIDeveloperInTucson wrote: > > > > > > > > > I'm not storing the translations in the cookie, just the language key > > that tells the script on the page which language to use on the client- > > side translation. > > > I am not planning on feeding the translations back to my server, at > > least not as long as I can ensure that google's service is running, > > which most of the time, I suspect it will be. > > > Akamai's DSA has me confused as whether there's some client-side > > element that would get cached to an edge server such that if a first- > > time user in, say, Japan translates the site, anytime anyone pulls a > > page from the Japanese edge server, they get the translated version, > > whether they want it or not. I do not THINK this is something that > > would happen, but I don't exactly know, and until I can figure it out, > > my VP won't let me work on building such a feature into our site, > > despite it being a necessity. > > > Thanks for your input, btw. > > -DevGuyInTucson > > > On May 25, 3:16 pm, Jeremy Geerdes <jrgeer...@gmail.com> wrote: > >> If your translations happen server-side - i.e., the client browser > >> contacts Google directly - I don't see how or why this would affect > >> anything that you are doing on your servers. Unless, of course, you were > >> feeding the translation response back to your servers. The question would > >> be: how do you intend to stash complete translations of your site in > >> client-side cookies? And why would you want to do it? I guess I would run > >> the translations for them, cache the different languages that you get > >> (i.e., you can cache Translations API results for up to 15 days). But I > >> guess I don't really know what you're up to, and I've never worked with > >> Akamai, so I don't know the technical capabilities that you're working > >> with. > > >> Jeremy R. Geerdes > >> Generally Cool Guy > >> Des Moines, IA > > >> For more information or a project quote: > >> jrgeer...@gmail.com > > >> If you're in the Des Moines, IA, area, check out Debra Heights Wesleyan > >> Church! > > >> On May 25, 2011, at 4:32 PM, UIDeveloperInTucson wrote: > > >>> For starters... > >>> Hopefully my questions here will lead to a robust discussion about the > >>> issues related to working with the DSA (Dynamic Site Acceleration) > >>> service provided by Akamai. > >>> It's my experience that the service works quite well for most of our > >>> needs, however there are times when we run into issues with the > >>> service caching content, and not pushing new content without clearing > >>> the edge servers' cache manually. This is usually not an issue, but > >>> I'm about to embark on the task of writing a script that dynamically > >>> translates our site content. > > >>> My understanding of it is as follows: > >>> If I employ a method using the language API that translates the text > >>> content of any page of my site via a client-side call to the > >>> translation object, it should have no effect on the cached content > >>> present on the edge servers. Is this correct? > >>> Additionally, if I set a client-side cookie that maintains the > >>> translation across the site, will this also be unaffected by the DSA > >>> cache? > > >>> I am working with a VP-level individual who seems to think that > >>> there's some conflict at work here, and I just want to be sure that my > >>> ducks are in a row before I say that he's incorrect. > > >>> For the record, I like Akamai. > >>> Thank you all for any feedback you can provide. > > >>> -- > >>> You received this message because you are subscribed to the Google Groups > >>> "Google AJAX APIs" group. > >>> To post to this group, send email to > >>> google-ajax-search-api@googlegroups.com. > >>> To unsubscribe from this group, send email to > >>> google-ajax-search-api+unsubscr...@googlegroups.com. > >>> For more options, visit this group > >>> athttp://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 > > google-ajax-search-api@googlegroups.com. > > To unsubscribe from this group, send email to > > google-ajax-search-api+unsubscr...@googlegroups.com. > > For more options, visit this group > > athttp://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 google-ajax-search-api@googlegroups.com. To unsubscribe from this group, send email to google-ajax-search-api+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-ajax-search-api?hl=en.
