Hello fellow developers, I've implemented an on-the-fly, client-side reverse-geocoding solution for the product my organization is building. It uses the ClientGeocoder class/service from GMaps Flash API to make all its calls. One component of the ClientGeocoder we were looking forward to leveraging is the internal cache (which the API Reference documentation describes), so that subsequent identical reverse- geocoding requests would not make a return trip to the server. While testing with Fiddler (the HTTP debugging proxy), I've discovered that the cache only seems to work when using the web application from Internet Explorer. When I test the web application with Firefox, Chrome, or Safari, _all_ reverse-geocoding requests go to the server, no matter how many identical reverse-geocoding requests have occurred previously. I was wondering if anyone knew why that is. Has anybody else seen this behavior? Is it a problem with the library?
Please advise. Thank you. Onyx using v1.18 -- You received this message because you are subscribed to the Google Groups "Google Maps API For Flash" 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-for-flash?hl=en.
