Notes from GeoServer mailinglist discussion

(The notes below are paraphrased to make them more concise. Apologies if I misinterpreted anyone, the whole thing can be found on Nabble)

cholmes:

1. communicating to GeoServer with the http using the regular WMS interface
2. communicate most of the information layers etc through WMS and perhaps REST interfaces
3. REST API on JTileCache to set those configurations
4. It should just be able to ship as a jar with geoserver
5. persist its settings to the (Geoserver) data_dir.
6. Ability to cache KML , other datatypes

sfarber:

1. cache-control headers

Per-Olof:

1. Make cache key stragegy pluggable
2. Make cache population thread safe / race condition safe.
3. Make internal tile representation a reference to data, not the data

jdeolive:

1. write this as a geoserver "service" for performance reasons, wrap the jtilecache servlet in a spring "interceptor", inject into the request processing chain before and after a WMS service call. Pluggable via the spring applicationContext.

aaime:

1. register a listener in the spring application context (contrast to jdeolive: you still use the spring context, but jdeolive there meant to integrate tilecache in the geoserver request processing)