Best thing I can suggest is to read more into what Ben was suggesting with checking the data that you are requesting and everything, and then throttling your requests down to a level that appears to be acceptable by Google.
On Fri, Jul 2, 2010 at 9:31 AM, JavaJive <[email protected]> wrote: > Thanks, but timers are no problem. > > However, I don't want to go blundering around in the dark trying to > second guess Google's limits, and maybe exceeding them in obscure > situations. I'd rather have something that I can guarantee to stay > within limits wihich are known and understood by both parties. > > On Jul 2, 3:26 pm, Nathan Raley <[email protected]> wrote: > > I never saw mention of what the specific rate is; however, they do > mention > > that there is one and that they have prevention mechanisms to keep people > > from scapping their databases. The person in the post that Rossko used > was > > rate limiting his requests to limit how fast he was tossing out requests. > > You could easily implement something along these lines with some clever > > timer usage. If you need some help with timers let me know. > > -- > 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]<google-maps-js-api-v3%[email protected]> > . > For more options, visit this group at > http://groups.google.com/group/google-maps-js-api-v3?hl=en. > > -- 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.
