We would recommend using Maps API v3 inside a browser control for iPhones, as there would be no limiting issues there. If you are using the HTTP Geocoding API now and aren't using an enterprise client ID or some non-IP identifier, then we would count requests against your IP, and you would likely run into the issue quite fast. So, I would suggest thinking about your expected load if that's the plan, and looking into other options or contacting us. But, those recommendations do not excuse us from breaking your apps. I apologize that we messaged that this was not going to happen, and that we didn't find a better way to contact potentially affected apps.
We'll check the logs to see the amount of breakage, but I think that we will be retaining this change, as it improves our authorization code and makes apps less likely to break in the future. (A necessary evil). Feel free to contact me offline regarding best strategy for your iPhone Apps. - pamela On Tue, Oct 20, 2009 at 6:17 AM, Rossko <[email protected]> wrote: > > > The JavaScript client-side geocode is unusable in iPhone devices... > > The HTTP method is the only practical one. > > Doesn't change Google's recommendation not to use it in that kind of > application. > Google is of course not the only HTTP geocoder, but you/they would > have to read the packet carefully for those too! > > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
