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. That could also be a possible problem, that was why I recommended reading more into the details of what Ben and them were trying to discuss in the original source that Rossko had sent you. It could be something wrong in the request you are sending or you could be sending too many at once and had reached the counter.
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. On Fri, Jul 2, 2010 at 12:01 PM, JavaJive <[email protected]>wrote: > Thanks both for your help. > > As far as I can see, what I'm trying to do is not against Google's > T&C, and in normal use is not likely to occur more than about 25 - 50 > times a day, far less currently. I don't see why there should be a > difficulty with it. > > In testing from my home postcode, 7 queries are sent to the Elevation > Service, the last 2 of which were being rejected. Therefore, > suspecting the maximum number that could be outstanding at any one > time was 5, I created a counter to wait for the number pending to fall > below 5 before sending more, but the two that had to wait were still > rejected with the OVER_QUERY_LIMIT response. > > This is what I mean by floundering around in the dark. > > Can Google please give us some precise T&C with numerical usage limits > and rates for the successful use of this service? > > On Jul 2, 4:16 pm, Rossko <[email protected]> wrote: > > > I'd rather have something that I can guarantee to stay > > > within limits wihich are known and understood by both parties. > > > > The classic example of smart throttling code - > > http://econym.org.uk/gmap/geomulti.htm > > this is geocoding for v2, but the principles are equally applicable > > here. > > -- > 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.
