Issue 17 in geodatastore: Caching KML or writing to disk

[codesite...@google.com]

Issue 17: Caching KML or writing to disk
http://code.google.com/p/geodatastore/issues/detail?id=17

Comment #3 by pamela.fox:
See r29. I memcache all geometry queries that are standard (no extra
queries like
bounding box), and also memcache the GeoRSS template. I clear the memcache
whenever
something is added/edited/deleted.
I haven't memcached the actual KML output, so that might still be slow
(though the
query retrieval aspect should be fast). I kind of want to convert that to
use Django
templates first, for consistency with the GeoRSS output.

--
You received this message because you are listed in the owner
or CC fields of this issue, or because you starred this issue.
You may adjust your issue notification preferences at:
http://code.google.com/hosting/settings