Using KmlLayer (triggered by the "idle" event after the map is zoomed
or panned) I'm loading a dynamically generated .kmz file.
The .kmz file is generated from the database and served directly from
memory. It's never actually a file on the server.
This part is all working as expected.
But for each request that my browser makes for this file, Google's
server make 34 requests for the same file!
These all have the same IP address (66.249.85.2) and identifier ("Kml-
Google; (+http://code.google.com/apis/kml), gzip").
I imagine this is because Google is taking a distributed approach,
with different processes each generating one tile to be sent back.
Yes, I can cache the file and serve up the cached file (so only the
first hit affects the database), which I plan to do anyway, but having
the Google servers request the same file 34 times simultaneously seems
like bad form.
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.
--
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.
