On Jul 3, 7:18 am, Rossko <[email protected]> wrote: > > This is why I want hard facts > > There probably aren't any hard facts available. > In the past, Google have been evasive/flexible (depending on your > degree of paranoia) about rate issues on the other rate-limited > services. > There is no reason for them to publish their anti-abuse > implementation in detail ; there is no reason why the parameters it > operates under should stay constant from minute to minute. > There are recognised methods to deal with the situation, and > throttle request rates to good advantage. They've been successfully > used for years. > > Deal with it, or ask for your money back.
the issue here is whether google's implementation is working correctly or not. There might be a bug in their implementation which is causing the problems that JavaJive is reporting in this thread. The mechanism for this service is implemented in javascript, and I can see the parameters, and how the mechanism works, but I don't yet understand how it is supposed to reset the throttle once 1024 locations have been processed. There is a reset function but I can't yet see where it is called. -- 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.
