Fair enough. Granted my example sucked but I'm not entirely sure the underlying idea - detection of a tile request failure - is that crazy. For example, if one of your tiling servers was an Amazon node that went down in that last outage, a certain portion of your tiles just wouldn't get loaded until the (js) code was updated to take that node out of circulation. I guess the moral of this is that if you care enough to not be down or degraded, you need to take the responsibility on yourself. Point taken.
Appreciate the response. On May 13, 12:46 pm, Barry Hunter <[email protected]> wrote: > To be honest it sounds like a horrible way to do handle it. > > Better would be to use a CDN that acts as a reverse (caching) proxy. Then > its all seemless. > > Or can you maybe setup the CDN, to issue a redirect on 404? That redirect > goes to custom handler. > > On 13 May 2011 12:11, Matt Alonso <[email protected]> wrote: > > > -- 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.
