With the google.maps.KmlLayer implementation, I can't think of any reason you'd want to do this (not saying there isn't one). Regardless of the size or amount of data in your kml file, the impact to the client browser is basically the same - that is to say slightly more than an image tile layer.
What are you trying to accomplish? -- You received this message because you are subscribed to the Google Groups "Google Maps JavaScript API v3" group. To view this discussion on the web visit https://groups.google.com/d/msg/google-maps-js-api-v3/-/L4MPNVVMC38J. To post to this group, send email to google-maps-js-api-v3@googlegroups.com. To unsubscribe from this group, send email to google-maps-js-api-v3+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-maps-js-api-v3?hl=en.
