On Wed, Dec 2, 2009 at 11:03 AM, Ben Appleton <[email protected]> wrote:
> On Wed, Dec 2, 2009 at 2:54 AM, bratliff <[email protected]> wrote: > >> The group interface is clobbering URLs. > > > What is a "group interface"? > Oh, sorry I misunderstood: you mean that the Google Groups user interface is destroying URLs that you paste into threads? > > >> The following link is an >> example: >> >> www.polyarc.us/sparse >> >> Tile server reliability seems to have deteriorated recently. Some >> tiles never arrive. > > > This would be a serious issue. I have loaded your site in FF3.5.5/WinXP > and panned around for a while. I wasn't able to replicate the issue you > describe even after loading hundreds of tiles. Which browser are you using? > > >> Switching from/to the same zoom level does not >> force reloading. > > > If tiles load as expected, there should be no need to forcibly reload. > > >> Examining the DOM, the tile slot contains a >> "transparent.png" place holder rather than an actual tile image. The >> only way to load the tile is to reload the application. >> > > Thanks for the info: that seems to imply the tile 'onload' never fired. > I'm not able to replicate this issue locally (perhaps I have a high > bandwidth or reliable connection). If you could grab a screenshot and/or > HTTP trace showing that tiles load late or never, that would be really > helpful. > > >> Perhaps the optimizer is being a bit too clever. If the API thinks >> the tile is already loaded, it will not attempt to load it again. >> Well, I believe it is a horrible idea. If the tile is already loaded, >> it will be served quickly enough from the browser cache. If the tile >> never arrived, it ought to be requested again. Every zoom change >> ought to reload every tile. A slight delay is preferrable to an >> incomplete map. >> >> It is unclear why "transparent.png" is even being used. If it is to >> disguise progressive rendering, it can be achieved in the onload/ >> onerror event handlers with "this.style.display" or >> "this.style.visibility". The use of a "background-image" is another >> option. >> >> A "watchdog" thread might improve reliability. Periodically, it could >> look for lazy tiles. If a tile has exceeded a resonable waiting >> period, the request could be reissued. >> >> this.src=this.src; >> >> will do the trick. >> >> -- >> >> 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]<google-maps-js-api-v3%[email protected]> >> . >> For more options, visit this group at >> http://groups.google.com/group/google-maps-js-api-v3?hl=en. >> >> >> > -- 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.
