On Jul 2, 6:14 pm, Nathan Raley <[email protected]> wrote: > Well, Ben had pointed out that there are means in which to protect against > bad requests being sent over and over requesting the same data.
Requests made individually using the same initial data by the same function work for both transmitters the requests of which are being rejected in batch mode, so there is nothing wrong with the requests that are being sent. > you could be sending too many at once and had reached the > counter. I think we've established that this is the case. However, unitl I know the exact parameters behind the rejections, I can't circumvent them with any assurance of my app always working, or as nearly so as one can ever get on the web, while remaining within Google's T&C. > That post that Rossko had linked in the later message regarding the > throttling provides a perfect example of how you can throttle your requests > and I would highly recommend trying to implement something along those lines > to help you trouble shoot this even more. I would have thought that waiting for the earlier results to return, as the above test did, would have been the best possible way of doing it, because that prevents the server(s) being overloaded, however fast or slow it/they and the internet are working. But apparently not. -- 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.
