A few other things worth trying:
1. clearOverlays followed by a series of addOverlays
If it works without memory leaks, you can avoid reloading the API. It
may work for Firefox but not for Internet Explorer in which case you
have to use a different approach for each browser.
2. Keep your status information in a parent frame with your map in
an iframe
Periodically reloading your iframe will refresh the API without losing
your status information.
3. Use "window.location.replace()" with optional parameters
containing status information.
"windows.location.replace()" will not add extra junk to your history
list.
The optional parameters could be:
¢er=
&zoom=
&layer=
&overlays=
which you can parse from your "window.location.href".
4. Use a static map instead of a dynamic map eliminating the API
Fewer moving parts
Fewer fragile pieces to break
Light weight
Very fast
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Google Maps API" 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-API?hl=en
-~----------~----~----~----~------~----~------~--~---
