On Mar 15, 5:15 pm, "Joe [www.IoniaSolutions.com]" <[email protected]> wrote: > From all my tests it looks like requests for geo-coding are limited by > public IP address that the request came from. Seems silly though..
But it's the only way of ensuring that the service isn't overloaded. If the geocoder took note of an X-Forwarded-For header, that header could easily be spoofed. Until there is an issue logged for salesforce.com at http://code.google.com/p/gmaps-api-issues/issues/list Google are unlikely to do anything about it -- and even if they do it will only be to raise the daily quota. They almost certainly won't change the rate limit. It would be good to list affected public ip addresses in that issue. Note that using a platform such as salesforce.com for *hosting* is not in the same class as using (say) a *client* routed via a mobile telephony proxy. Google may decide not to cater for such shared hosting. But you won't know if there is no issue raised. -- You received this message because you are subscribed to the Google Groups "Google Maps API" 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-maps-api?hl=en.
