I've read that, and it takes much longer than a mere 100ms for the requests to return. Therefore, if implementing that delay between requests works, waiting for the server to return the first batch before sending any more should be comfortably more than adequate, shouldn't it?
I've tried reducing the number of pending requests to 4, but one still gets rejected. I dare say 3 might do it. But will it work tomorrow, let alone next year? This is why I want hard facts, not suggestions made in the light of no greater knowledge than I myself have! The links provided have at least told me the daily quotas, which I couldn't find before, so thanks for those, but I need to understand *exactly* why I'm getting this message. On Jul 2, 7:39 pm, Nathan Raley <[email protected]> wrote: > Rossko pointed you to the site:http://econym.org.uk/gmap/geomulti.htm > > <http://econym.org.uk/gmap/geomulti.htm>In this post, if you view the > example, he provides you with a means of which to throttle your requests, > complete the entire query, and have it working 100% of the time no matter > how long the responses take. I suggest reading into the example he provided > and taking a look into that b/c that is exactly what you are looking for. -- You received this message because you are subscribed to the Google Groups "Google Maps JavaScript API v3" 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-js-api-v3?hl=en.
