On Mar 8, 12:50 pm, bratliff <[email protected]> wrote: > On Mar 8, 5:50 am, Ben Appleton <[email protected]> wrote: > > > > > We now queue image requests in JS, only fetching at most 12 images at a > > time. This allows to cancel requests if a tile falls out of view before the > > request has been forwarded to the browser, which reduces latency for a quick > > sequence of zooms. To recover from stalled tiles we abandon a tile fetch > > after 2 minutes. > > > This can still fail in a few ways: > > > - The bandwidth could be so low that loading 12 tiles x 25kB = 300kB > > takes more than 2 minutes. > > - The internet connection could drop out temporarily. > > - The page could be making many other HTTP requests, blocking our tile > > requests. > > > I appreciate your feedback; we haven't finished optimizing tile loading yet. > > > The API does not reload a discarded tile if it returns
I am experiencing approximately 10% to 15% failure rate. I wonder if my ISP is throttling my requests. Perhaps HTML & JS files receive priority over JPEG & PNG files. Perhaps too many requests to the same domain are demoted to lower priority. I agree dial-up is a relic of the past. I have learned to live with slowness but not unreliability. For now, I am forced to use V2. -- 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 [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-js-api-v3?hl=en.
