A Script on This Page Has Stopped Responding

Hello,

I have a map that pulls all of the addresses from a CF recordset. However once my client added more than roughly 10 address I now receive a message from the browser stating that "A script on this page may have stopped responding or may be busy etc..." I can click cancel or continue, if I continue the map does load with all of the flags that represent the addresses in the DB. However this script warning is really annoying, also the load time is horrible.

What do I need to do to get this to function properly?

You can view the script warning here:
business-map.cfm

Thanks,
Paul

I am still baffled by this huge lag, WA Docs state I can map from a recordset and makes no mention of limitations or lag of any kind.

I have been tracking the average time of the recordset query and that is roughly 31 milliseconds for it to pull all of the records, however the map takes so much longer to generate and that's after the script warning.

The only way I have seemed to be able to speed it up is by limiting the number of records returned to under 10 and that renders the recordset feature pretty useless.

I know that it takes time for google to plot these addresses but this seems way over the top.

Any thoughts on this is greatly appreciated.

Thanks,
Paul

Google has restrictions on the number of requests per second... so we purposely add a delay to get around that problem.

We are working on a free dot release update that will cache the data points so that google won't be needed for geocoding after the first display. This should resolve the problem. That update should be available sometime next month. Until then I'm afraid there is little that can be done to show more than a dozen points before Google starts rejecting the reqeusts.

Hello Ray,

Did the update to 1.0.4 resolve the issue you described above?

"Google has restrictions on the number of requests per second... so we purposely add a delay to get around that problem.

We are working on a free dot release update that will cache the data points so that google won't be needed for geocoding after the first display. This should resolve the problem. That update should be available sometime next month. Until then I'm afraid there is little that can be done to show more than a dozen points before Google starts rejecting the reqeusts."

I don't want to get my clients hopes up again and have it crash...

Thanks,
Paul

It should have... but as an engineer I would suggest ttrying it and verifying that was indeed the issue in the first place before getting hopes up too high. But this should fix it if I was right in my first diagnosis of the problem.