Darin Fisher wrote:
..
> uses just the disk cache. This is changing though. Our plan is to
> replace the current cache with a much more robust, maintainable, and
> extensible design. This work is already underway, and the new cache
> interfaces will provide methods that would allow you to determine if a
> particular URL is in a particular cache.
>
I suspect a bug in the current disk cache in current builds (although an
URL is cached and the ID is found in the DB, sometimes the file is still
retrieved again over the net). Before I file another bug, I'd like to
investigate further and maybe provide a patch.
However, if the cache is currently being rewritten, this could be
superfluous and I might rather wait.
Dow you have more info on the timeline? Where can I ask questions
regarding the disk cache in order to track down the problem?
Cheers, Nils
