May be you can delegate the geocoding job to the client side using js ? also you can take a look here : http://gaengine.blogspot.com/2010/11/world-countries-and-ip-geocoding-api.html
Nick ;-) On Apr 6, 7:25 pm, Joe Tyson <joety...@gmail.com> wrote: > Hello, > > This seems to be more of a problem with the geocoding api than app engine, > but I'm unable to get ahold of anyone on that team so I'll post here > instead. > > The new Geocoding API doesn't do any form of url signing or api keys for > non-premier accounts and resorts to using IP address to control quotas. > Since App Engine uses a shared IP pool, my app gets clumped in the quota > limitations of other apps. This must be a somewhat frequent problem for > other apps, since 90% of my geocoding attempts get an 'OVER_QUERY_LIMIT' > message. These last few days, it has been closer to 100% at 500-600 queries > spread out over an 15-20 hours. > > I'll add that I don't think using a pool of IPs is at all the issue. Any > large scale deployment would be hitting the Geocoding API from a pool of > IPs, and if the pool were dedicated to a single service, the service would > be circumventing the Geocoding API quotas anyway. > > Is anyone else on the list having this issue? Have you been able to work > with the geocoding team to get auth tokens that don't require having a > premier account? > > joe -- You received this message because you are subscribed to the Google Groups "Google App Engine" group. To post to this group, send email to google-appengine@googlegroups.com. To unsubscribe from this group, send email to google-appengine+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en.
