On Jul 4, 8:38 am, JavaJive <[email protected]> wrote:
> Correction, I missed an error for GESLimit = 4.  So the results were:
>
> 1:      Good
> 2-3:    1 x OVER_QUERY_LIMIT error
> 4-5:    2 x OVER_QUERY_LIMIT errors
>
> In all cases, as one would expect, the errors came on the request(s)
> sent last.

that's interesting.  I'll see if I can replicate these results.

One thing I've noticed using Firebug is that the OVER_QUERY_LIMIT
seems to be implemented on the client side, because the requests when
over the limit aren't sent to the server and the OVER_QUERY_LIMIT
error is very quick (50ms - 100 ms).  Also caching is being used so
it's important to clear the cache when repeating these kind of tests.

-- 
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.

Reply via email to