"Internally the CallbackFS driver delays closing of files in hope that these files will be opened again soon and data structures that were created internally by the driver for the files will be reused. Use this method to allow or forbid such behaviour."

At present with the property set to false, I appear to be getting too many file closes. For instance, when a text file is edited in notepad, when the new content is saved I am getting 3 opens and closes - presumably for content/date and attributes. When set to true, the file does not close when expected and I am delayed in updating my underlying database.

What is the period of delay? Surely this should be a user-defined parameter somewhere.

This parameter may be deprecated, but the CallAllOpenCloseCallbacks property is not and that one also affects whether you see the close of a file or not. The current documentation for it is also incorrect, it states that when the property is TRUE that the callbacks are not called! and that is wrong. I have the property set to TRUE in my application and all the callbacks are called. When you set the property to FALSE is when the callbacks do not get called.

It would be nice, Vladimir or Eugene, if you fixed that piece of doc. :-)

Otherwise, everything is going pretty well for my application and CBFS, I'm just waiting patiently for the next build.

We use cookies to help provide you with the best possible online experience. By using this site, you agree that we may store and access cookies on your device. You can find out more about and set your own preferences here.