On Thu, Apr 7, 2011 at 3:20 PM, nickmilon <[email protected]> wrote: > IMHO a proxy will complicate things. > What about if GAE team gets in touch with maps V3 team and explain to > them the issue so may be they can rate limit all GAE originated appls > by app id which is a very secure method since app id can't be > hacked ?
Unfortunately this would incentivize the rest of the world to start *adding* GAE headers to work around maps' ratelimits. But combined with knowledge of the IP pool that appengine fetches from, it's a great idea. BTW, a proxy is pretty trivial to set up. And you can use it for other services that have rate issues as well - I've run into several. Jeff -- You received this message because you are subscribed to the Google Groups "Google App Engine" 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-appengine?hl=en.
