[Geoprisma-dev] Caching for the Proxy
Yves Moisan
yves.moisan at boreal-is.com
Thu Jan 28 15:35:49 EST 2010
> > for things to get cached. At first, I tried to cache just TileCache,
> > but that did not seem to work.
> Could you please fill a ticket for this ?
In the end, I was looking at php-cgi calls that were MapServer related.
My mistake. I see the right response headers. Sorry for the noise.
>
>
> > Anyhow, I didn't go into the code really
> > but if I set client-side caching like above, does it mean new edits in a
> > PostGIS table (served by MapServer) could go unnoticed for 2419200
> > seconds = 28 days ? Nothing can tell Apache if something has changed
> > from what I can see, so it seems to me we'll have to tell users to clean
> > their cache often for layers they edit ...
> >
> In that case, you would use no caching for WMS only.
>
>
> > Eventually, I think caching should be a datastore option.
> This adds a lot of complexity in my opinion and should be avoided. The
> primary goal of caching is : performance. Turning it on should come
> with some minor drawbacks, such as having an edited layer unchanged on
> the wms image but really changed on the vector side.
Right. We'll see how it goes and I'll tell folks here to just cache TC.
Cheers,
Yves
>
> My 2 cents,
>
> Alexandre
>
More information about the Geoprisma-dev
mailing list