Hi all, Thanks for the replies. I am coming to the conclusion that the KmlLayer cannot be trusted to reliably display - and that I can see no reliable workaround. Is anybody confident that the KmlLayer is reliable?
At this point I am considering using individual encoded polylines. The panning experience for the user is slower but at least the map should display reliably. Tiim Haverland at [1] and [2] claims that WebKit browsers cache the results of the KmlLayer call - *even if the call failed*. This means that retrying will not work in WebKit browsers. I have repeated his results with Chrome and Safari. This was with a path which was dynamic. It was set when a page loaded and retries would continue on the same path. I had the file cached in memory and my logging showed it was served within 3s. An alternative approach would be to use the same filename and rely on Google's servers caching the result. I don't like this because: 1. It becomes more difficult to protect my content. The dynamic filename method added a level of difficulty to taking the content. 2. If the first request comes from a WebKit browser then that may fail for that user - an no retrying will help. Alternatively, I could cache yet more aggresively using a content delivery network. Thanks, Edward Links: [1] http://code.google.com/p/gmaps-api-issues/issues/detail?id=3617 [2] http://groups.google.com/group/google-maps-js-api-v3/browse_thread/thread/ead45965777fc6a7/37a68c1ef29baa5c?lnk=raot On Nov 18, 9:40 am, Mike Dolbow <mike.dol...@state.mn.us> wrote: > I use the 'metadata_changed' event on the KMLLayer inside a listener so I > can tie the document load-up to the KML load. That way if the KML gets hung > up, the document shows a throbber and I know I have to either wait or > re-load. -- You received this message because you are subscribed to the Google Groups "Google Maps JavaScript API v3" group. To post to this group, send email to google-maps-js-api-v3@googlegroups.com. To unsubscribe from this group, send email to google-maps-js-api-v3+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-maps-js-api-v3?hl=en.
