[Geoprisma-dev] Caching for the Proxy

[Yves Moisan]

> >
> > The second option would relieve users from configuring client-side
> > caching in the php code and they would moreover allow users to easily
> > switch caching on/off or set different times to particular datastores.
> > That is individual data sets could be controlled and not only WMS ot TC
> > service types.
> >   
> 
> Mmm.  I'm not sure anymore.  I wouldn't go that far since we sometimes 
> combine Resources together to make OpenLayers layers.  

Good point.

> What if some 
> DataStore have <cache> turned on and others off ?  Plus, it adds a lot 
> of complexity (having to add these 2 nodes to each DS).
> 
> The need is : performance boost !  Simply turning the client-side 
> "caching" on or off for the whole system seems really fair and simple 
> enough.  I still agree that we should have WMS and TC separated though.

I'm not against implementing an on/off switch as long as we at least
have separate controls for WMS and TC.  We'll see if a per datastore
approach is needed after.  

Thinking about it : we usually have one datastore per service type for a
particular resource, e.g. one wms datastore and one TC datastore so
being able to control caching for both service types independently is
equivalent to specifying it in the datastore xml node.

> 
> What do others think ?

Indeed.

Yves
>