> OK, I understand now the VSICachedFile lifecycle and it makes sense. But
> then the disk cache should not be used at all for files in
> the CPL_VSIL_CURL_NON_CACHED variable.
Indeed. The cache disk code hasn't been touched/tested in years, and
CPL_VSIL_CURL_NON_CACHED was added afterwards.
>
Hi Even,
Long time no see!
On Fri, Jan 5, 2018 at 12:21 PM, Even Rouault
wrote:
> > 8) In the case discussed in 7), CPL_VSIL_CURL_NON_CACHED will just purge
>
> > the data from 1 the 3 caches: papsRegions. The vsil_cache and the disk
> will
>
> > still cache the content.
>
>
>
> CPL_VSIL_CURL_N
Hi,
> 1) There are a lot of knobs that can be used to tune the thing that are not
> documented. For example CPL_VSIL_CURL_USE_CACHE. Is it on purpose?
Yes, the disk cache is an experiment that isn't used anywhere (from what I
know) and likely
not in a finished state as you noticed in your below
Hi,
I've been looking at the performance of GDAL in the context of MapServer
and QGIS accessing GeoTiff on a HTTP server (S3, mostly).
Doing that, I had a good look at the cpl_vsil_curl.cpp file and the
surroundings and that raised a few questions/concerns:
1) There are a lot of knobs that can b
