Google seem to have imposed timeouts on the tile fetches. That's fine for Google tiles that are provided by fast servers, but if you have a slow server, it looks like the API doesn't always wait long enough before giving up and deciding that the fetch has failed.
I noticed that fetching an individual tile from a page that exhibits the problem wasn't much any longer than fetching an individual Google tile. The significant difference was that the Google map types were fetching more tiles at once, so the total time taken to fetch all the tiles was significantly shorter. Google achieve this effect by using aliases to break the browser connection limits. I can't reproduce the effect on my pages. The webserver that I use just isn't slow enough (my webhost doesn't provide GD, so I can't even build a slow tileserver script). I think that this technique might possibly get round the problem. It certainly speeds up custom map tile fetches http://econym.org.uk/gmap/custommapparallel.htm -- http://econym.org.uk/gmap The Blackpool Community Church Javascript Team --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Google Maps API" group. To post to this group, send email to Google-Maps-API@googlegroups.com 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 -~----------~----~----~----~------~----~------~--~---
