Hi Jeff, Thanks for the explanation. The caching so far I did for my web application is that I reserve the image link (thumbnail and image) on behalf of my user for image gallery view. If they need to reload the image, they press a 'reload' button.
For that common rule you provide, is that for per user or per application ? If for application I think that may not be enough if we have a ton of users base and get very high traffic requests to picasa. Thanks, Feris On Fri, Nov 21, 2008 at 4:03 AM, Jeff Fisher (Google) < [EMAIL PROTECTED]> wrote: > > > While we reserve the right to go after abusive API use and introduce > API quotas if necessary, I don't think that you are likely to run into > this if you are simply performing actions on behalf of a user. Some > caching on your part (memcache, a local image store) is always > appreciated. > > One rule of thumb I've heard often with Web APIs that don't have an > explicit limit is to keep your traffic under 1 QPS (query per > second.) > > Cheers, > -Jeff > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Google Picasa Web Albums API" 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-Picasa-Data-API?hl=en -~----------~----~----~----~------~----~------~--~---
