On Tue, Dec 17, 2013 at 4:17 PM, Jeremy McLain
wrote:
> 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."
>
What proxies are you using? Are these proxies giving you new IP addresses
when you use th
An issue has been opened. Actually is a feature
request: https://code.google.com/p/gmaps-api-issues/issues/detail?id=2844
--
You received this message because you are subscribed to the Google Groups
"Google App Engine" group.
To unsubscribe from this group and stop receiving emails from it, se
engine@googlegroups.com
> [mailto:google-appengine@googlegroups.com] On Behalf Of David Wursteisen
> Sent: Wednesday, July 06, 2011 1:24 AM
>
> To: google-appengine@googlegroups.com
> Subject: Re: [google-appengine] Re: HItting query limit using Geocoding API
> from App Engine
>
&
limited have this.
From: google-appengine@googlegroups.com
[mailto:google-appengine@googlegroups.com] On Behalf Of David Wursteisen
Sent: Tuesday, July 05, 2011 11:51 PM
To: google-appengine@googlegroups.com
Subject: Re: [google-appengine] Re: HItting query limit using Geocoding API
from App Engine
e-appengine@googlegroups.com [mailto:
> google-appengine@googlegroups.com] *On Behalf Of *David Wursteisen
> *Sent:* Tuesday, July 05, 2011 11:51 PM
>
> *To:* google-appengine@googlegroups.com
> *Subject:* Re: [google-appengine] Re: HItting query limit using Geocoding
> API from App En
s.com
Subject: Re: [google-appengine] Re: HItting query limit using Geocoding API
from App Engine
is an issue was created for this problem ?
Maybe we can create one if not.
http://code.google.com/p/gmaps-api-issues/
2011/4/9 nickmilon
Jeff
You are right Google IP pool + app id is what is n
is an issue was created for this problem ?
Maybe we can create one if not.
http://code.google.com/p/gmaps-api-issues/
2011/4/9 nickmilon
> Jeff
> 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 wrote:
> > On
On Thu, Apr 7, 2011 at 3:20 PM, nickmilon 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
>
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
ril 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 by
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
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
e
12 matches
Mail list logo
