I was just curious as to the behavior of Overlay.Refresh(), particularly when many calls to it come in at a short period of time... Does Overlay queue these up and execute each refresh, or if there is already one queued up to go, does it throw the rest away?
I'm running into an issue that without looking into it too much I think is caused by the refreshes being queued up and executing (specific to my case a WMSRasterLayer as download from WMS server can be slow). Anyhow, just knowing how Refresh works will help me determine the best way to go about figuring out my issue.
Thanks,
.Ryan.