google-code-export / geoxml

Automatically exported from code.google.com/p/geoxml
1 stars 1 forks source link

Caching with geoxml #53

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago
Anyone doing this? Obviously Google caches KMLs, but this doesn't seem to be 
the case with geoxml. The KML gets loaded in geoxml every time on v3. What are 
the challenges? Am I off-base? 

Using Maps API v3 and v2. GeoXml for both as well.

Original issue reported on code.google.com by zephyrun...@gmail.com on 16 Nov 2011 at 7:59

GoogleCodeExporter commented 9 years ago
Not sure what the question is exactly. Googles caching is both a blessing and a 
curse. Making it harder to update a file without playing name games for 
instance.

Basically google pre-processes its kml into a form of json and that is what 
they store cached .... I havent worked(/tested) yet on the kjson element of 
GeoXml  v3 api (the raw code is just a translation at the moment and may have 
some issues with the poly elements because of that) ie its on my TBD list. 

GeoXml re-constructs sidebars and similar things as kjson loads so there will 
be some processing

Original comment by lanceala...@gmail.com on 16 Nov 2011 at 9:34