Hi Infeo,
Sorry for the delay. I totally missed this thread.
* The advantage of the FCB GC approach is
that it prevents filter drivers (Anti-virus)
* from
exponentially slowing down procedures like zip file extraction due
to * repeatedly rebuilding
state that they attach to the FCB header.
What is happening is that by default Dokan delete the FCB object
right after all handles on this file are closed (There is 1 FCB per file
regardless how many handless are open on it).
This release system resources that some filter drivers might
recognize as the file was removed. If the file is reopened right after, the
filter drivers will reconstruct around the new instance which is fine but if
this happens on a large set of files, you will see the difference.
Why it is not enabled by default ? Just because I prefer to let
people choose to turn it on or not and not be surprised by a new "non vital"
feature being enabled by default.
Best regards,
Liryna