> A single user can easily trigger this every second, every time they > pan or zoom. It doesn't take much of that multiplied by 34 to swamp a > server.
They're trying to do you a favour ; Google keeps their own cache of KML layers .. presumably a distributed 34-copy one! At the moment you are defeating their cache perhaps? and increasing traffic. If you plan to stabilize the data, you needn't cache, Google will do that for you. Just serve up one big KML and let Google worry about tiling it to the client. Their model of KML use doesn't really expect dynamic "tiled" usage. I'm not sure if there would be any advantage in looking into KML regions with network links ; this can be used as a sort of native KML tiling. -- 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.
