"you get what you pay for"  I mean the GeoCoding API, not GAE.  I think the
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).





-----Original Message-----
From: google-appengine@googlegroups.com
[mailto:google-appengine@googlegroups.com] On Behalf Of nickmilon
Sent: Thursday, April 07, 2011 3:21 PM
To: Google App Engine
Subject: [google-appengine] Re: HItting query limit using Geocoding API from
App Engine

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 ?

@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-appengine@googlegroups.com 
> [mailto:google-appengine@googlegroups.com] On Behalf Of Joe Tyson
> Sent: Wednesday, April 06, 2011 2:59 PM
> To: google-appengine@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 
> ?
> also you can take a look here
:http://gaengine.blogspot.com/2010/11/world-countries-and-ip-geocoding...
> ml
>
> 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
athttp://groups.google.com/group/google-appengine?hl=en.
>
> --
> 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
athttp://groups.google.com/group/google-appengine?hl=en.

--
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.


-- 
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.

Reply via email to