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: [email protected]
[mailto:[email protected]] On Behalf Of David Wursteisen
Sent: Wednesday, July 06, 2011 1:24 AM
To: [email protected]
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 <[email protected]>

External Proxy, issue solved.  Not to be harsh, but all the API's that are
IP rate limited have this.  

 

From: [email protected]
[mailto:[email protected]] On Behalf Of David Wursteisen
Sent: Tuesday, July 05, 2011 11:51 PM


To: [email protected]
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 <[email protected]>

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 <[email protected]> wrote:

> 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]
<mailto:google-appengine%[email protected]> .
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 [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.

-- 

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]
<mailto:google-appengine%[email protected]> .
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 [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.

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

Reply via email to