Yes. After I finished posting last night, I briefly tried the same test in Opera v9.64, and was surprised to find that the results were different! There, GESLimit = 5 worked fine!
Consequently, having known of Firebug changing behaviour before, I tried disabling it, using my own Debug.js which simply adds a textarea to receive console.log messages, but the behaviour in FF3 was just the same, 2 errors for GESLimit = 5. I shall obviously have to waste time more precious time investigating this even more closely :-( On Jul 4, 3:22 am, William <[email protected]> wrote: > On Jul 4, 8:38 am, JavaJive <[email protected]> wrote: > > 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.
