HItting query limit using Geocoding API from App Engine
Joe Tyson
nickmilon
js ?
also you can take a look here : http://gaengine.blogspot.com/2010/11/world-countries-and-ip-geocoding-api.html
Nick ;-)
Joe Tyson
--
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-a...@googlegroups.com.
To unsubscribe from this group, send email to google-appengi...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en.
Brandon Wirtz
Use a Proxy. Then you can come through your own IP-pool.
nickmilon
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 ?
@Joe sorry my api isn't that useful in your case.
Regards
Nick
On Apr 7, 1:06 am, "Brandon Wirtz" <drak...@digerat.com> wrote:
> Use a Proxy. Then you can come through your own IP-pool.
>
> From: google-a...@googlegroups.com
> [mailto:google-a...@googlegroups.com] On Behalf Of Joe Tyson
> Sent: Wednesday, April 06, 2011 2:59 PM
> To: google-a...@googlegroups.com
> Subject: Re: [google-appengine] Re: HItting query limit using Geocoding API
> from App Engine
>
> We are delegating some of that to the client now, but it is far
>
> less than ideal. Our client is mobile, so every byte that we send
>
> over can end up costing our users money (you would be surprised
>
> how sensitive some people are to this).
>
> Thanks for the resource, though. I wish country level would be
>
> enough information for us :-(.
>
> Doing some additional searching around, it looks this issue has
>
> been bought up by some other users on the maps forum:
>
> http://goo.gl/RyJ9w
>
> On Wednesday, April 6, 2011 at 2:44 PM, nickmilon wrote:
>
> May be you can delegate the geocoding job to the client side using
> js ?
> ml
Brandon Wirtz
more ideal scenario is GeoCoding and other Google API's should require
registration and authentication.
Similar to another thread about blocking all of GAE, in many cases GAE
doesn't work with Free API's because of the IP limits and the number of
people exploiting GAE as a Proxy.
I will be the first to admit that my first Application on GAE was a simple
URL proxy for gaining access to GAE's IP Address Pool. Us early grey hats
peed in the pool and ruined things. (yes I suck but I'm trying to suck
less).
Ikai Lan (Google)
bFlood
http://www.google.com/enterprise/earthmaps/maps.html
Dev guide for Url signing
http://code.google.com/apis/maps/documentation/premier/guide.html
nickmilon
facing, password protected Web sites, while what we are talking about
here is the free Google Maps service, where G is penalizing all Apps
running on top of GAE since they have to share the ip addresses pool
of GAE ip adresses.
@Ikai : what you write applies to old maps (V2) API where you can
obtain an application authorization key and applications are rate
limited based on this key, although I feel that some kind of ip based
limitations exists also.
Maps V3 which is the way to go especially for mobile appls, do not
require an application key, instead there are rate limitations based
just on originating IP addresses, this puts GAE based appls on a
disadvantage since we have to share this with all other GAE based
appls using the service.
Regards
Nick
On Apr 8, 2:58 pm, bFlood <bfl...@spatialdatalogic.com> wrote:
> Google Maps Premiumhttp://www.google.com/enterprise/earthmaps/maps.html
>
> Dev guide for Url signinghttp://code.google.com/apis/maps/documentation/premier/guide.html
Jeff Schnitzer
> 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
nickmilon
You are right Google IP pool + app id is what is needed to make rate
limiting unhackable.
On Apr 9, 3:32 am, Jeff Schnitzer <j...@infohazard.org> wrote:
David Wursteisen
Maybe we can create one if not.
http://code.google.com/p/gmaps-api-issues/
Brandon Wirtz
External Proxy, issue solved. Not to be harsh, but all the API’s that are IP rate limited have this.
From: google-a...@googlegroups.com [mailto:google-a...@googlegroups.com] On Behalf Of David Wursteisen
Sent: Tuesday, July 05, 2011 11:51 PM
To: google-a...@googlegroups.com
Subject: Re: [google-appengine] Re: HItting query limit using Geocoding API from App Engine
is an issue was created for this problem ?
Brandon Wirtz
Why is an external Proxy a bottle neck to scale? If there is an API limit then as long as your proxy can handle the volume of the limit then it is not a bottleneck.
We have talked before about the fact that you can extend the number of Geocodes by building your own database of results, and by using rounding to limit the coding to the accuracy you need.
If you need more scale Pony up for Eagle or Maxmind.
Again you are looking to solve a problem by making a service you depend on change their behavior. This is the exact opposite of building for scale. When you require others to change their behavior you put your fate in their hands.
-Brandon
From: google-a...@googlegroups.com [mailto:google-a...@googlegroups.com] On Behalf Of David Wursteisen
Sent: Wednesday, July 06, 2011 1:24 AM
To: google-a...@googlegroups.com
Subject: Re: [google-appengine] Re: HItting query limit using Geocoding API from App Engine
I don't agree.
Used an external proxy will act as a bottleneck in a scallable system. And you'll have to manage this proxy too. (And I don't want to have to)
It's a good workaround, like use the V2 of Map API. But for me, it's not the right fix.
And I'll be happy with an "official" statement about this issue, even if it's a "won't fix"
Regards
2011/7/6 Brandon Wirtz <dra...@digerat.com>
David Wursteisen
Used an external proxy will act as a bottleneck in a scallable system. And you'll have to manage this proxy too. (And I don't want to have to)
It's a good workaround, like use the V2 of Map API. But for me, it's not the right fix.
And I'll be happy with an "official" statement about this issue, even if it's a "won't fix"
Regards
External Proxy, issue solved. Not to be harsh, but all the API’s that are IP rate limited have this.
Jeff Schnitzer
to swamp it, you're almost certainly going to bump into the geocode
rate limits again. The scalability limit isn't the proxy, it's the
rate limit.
In any case, this is probably something to take up with the Maps team.
Jeff
Jeremy McLain
Jeremy McLain
Vinny P
This is driving me crazy. I've tried three different proxies and I am still getting: "You have exceeded your daily request quota for this API."