geocode request rate

I have tracked down why my map page displays are inconsistent (sometimes less than the total number of map points are displayed). I am getting the 620 response code which means my request rate is too high for the server. This happens reasonably consistently after 10 requests. So does anyone have the javascript code for the wagmp_map_x.js file to monitor the error response and add to the delay between requests if over-running the server??

The newest version of pro maps should automatically cache the addresses once viewed, which should prevent geocache limits after viewing. Have you used the most recent version? Do you get any javascript errors on the page?

I am running 1.0.6. You can take a look at this page at testci.html.

There are some errors in the Firebug "all" listing, but they somehow seem to get resolved. In other words, the "file not found" errors don't correspond with the map that gets displayed.

The requests that return the "620" response are geocode requests, not cache read requests.

_xdc_._gg3rjfc4h && _xdc_._gg3rjfc4h( {
"Status": {
"code": 620,
"request": "geocode"
}
}

620 G_GEO_TOO_MANY_QUERIES The given key has gone over the requests limit in the 24 hour period or has submitted too many requests in too short a period of time. If you're sending multiple requests in parallel or in a tight loop, use a timer or pause in your code to make sure you don't send the requests too quickly.

Check to make sure that the cache file is written to with information about the addresses. If they are not being written to, there may be an issue with permissions for that directory/file.

I don't understand why you keep asking about the cache when I have told you I am getting an error message indicating my request rate is causing the problem. Is there some less than obvious connection between the two?

Incidentally, a lot of the problems being expressed on this forum could be related. If anyone wants to show more than 9-10 map points, anyone would seemingly have this problem. The code you are distributing would probably be less troublesome if it included the recommended error handling/wait loop.

Did you check the file or not?

If the cache file is written correctly, it eliminates the need to request geocoding from google's servers.

The file and its parent directory are set to 777, but there is no information in the file except for the header,

<?xml version="1.0" encoding="utf-8"?>


I guess I am still not getting it. Even if the cache file was working, which it apparently isn't, in order for the information to get there in the first place, the server still has to deliver the geocode information for all map points at least once, no?

You seem to be suggesting that it would be a reasonable solution for the cache to eventually get all correct entries by adding a few more good responses each time a page is refreshed?

I just took a look at your page and was not getting the error you are reporting. All the map locations load up correctly when I access the page. Which browser are you using to get this error?

I have Chrome, IE8, Mozilla, and Safari. Of the four, Mozilla is the only one that shows all 15 map points at present, and it doesn't do so every time. When it fails, Firebug shows the 620 error. Chrome, IE8, and Safari repeatedly show 8-10 map points only.

At no time is anything written to the cache file, as far as I can tell.

Oh, most importantly...Mozilla's good behavior aside, the reason it is working as good as it does at the moment is because I put some wait loops after every map point creation to slow it down. Not the correct way to do it, I know, but so far I haven't been able to make the js sleep function work. Something about catching the exception?