On Sat, 7 Jun 2008, Keith Hopper wrote:
In article <[EMAIL PROTECTED]>,
John-Mark Bell <[EMAIL PROTECTED]> wrote:
On Fri, 6 Jun 2008, Richard Porter wrote:
There is no point in cacheing local files.
Actually, there is -- it removes the overhead of reprocessing the file
content into whatever internal representation NetSurf uses.
Well! The vast majority of the use I make of a browser is to view
local files as I modify/edit them. My suggestion would be that there be a
Netsurf option to NOT cache local files in this kind of situation.
Why make it an option when, if the caching implementation wasn't currently
broken, it would make no difference? If the file's modified on disk, then
the cached copy is out of date and should be replaced, simple as that.
This is the exact behaviour of NetSurf in the past and, assuming I get
some time to investigate why it's currently broken, will be the behaviour
in future, too.
John.
