Function implementation and optimization

[ZhangHuan0407]

Hi all.
I like to type code,I'm currently learning how to make a network disk for myself.
I take the Mirror.cs in the example as a basis, transfer the request to another device via TCP, do the execution and return.
(After a request starts, until it returns, force lock)

I found some strange things:

Requests for the IDokanOperations2.GetVolumeInformation function more frequently.
Within 10 seconds of mounting the hard drive, 45 times.
It seems to me that what this API returns should not change after the hard disk is mounted?
Is Dokan calling this API so often a problem with Microsoft?
I want to cache the results of this API locally, because I guess the data it returns doesn't change.

Another thing, I expect to know which APIs can return DokanResult.NotImplemented directly without causing the explorer to crash.
For example, in the API below, I have never used this parameter.

I'm not sure how returning DokanResult.NotImplemented and DokanResult.Success affects the execution of GetFileSecurity?
Where should I go further to understand what DokanResult return values mean for the API?

[LTRData]

GetVolumeInformation is in many scenarios called very frequently. Applications and drivers that call it typically expect it to return fast, with possibly cached data if the data does not change. So in your case, I would recommend that you simply cache this information at the first call and after that simply return the cached data.

GetFileSecurity and SetFileSecurity can return NotImplemented if security descriptors are not preserved by the file system. Some other functions can return NotImplemented if they are not used, for example FindStreams is only required when DokanOptions.AltStreams is specified in drive options.