Filter:Pascal Plain C C++ (DLL/Lib) C++ (VCL) C++ (.NET) C# VB.NET Java
This event is fired when storage buffers must be flushed to media.
- Sender - reference to the class that called the delegate/event handler.
- FileHandle - Handle to the storage that needs to be flushed.
- Result - out parameter (return value for DLL) where the application places the result of the operation. If you are working with file system, Win32 error code is a good candidate for placing to Result parameter. Otherwise you can use any other error codes, just be sure that 0 means success.
[Java]See Description for details about error reporting in Java.
- [Plain C] UserData - application-defined parameter which is specified when creating the storage and passed back to callback function.
This event is fired when storage buffers must be flushed to media. If you are working with file system, call FlushFileBuffers. If you are working with remote location, the event handler must transfer all storage data to the remote location. Stream classes in VCL and in .NET Framework have Flush method.
The callback/event handler must be set before the storage is opened.
You need to implement ISolFSFileEvents interface in your code and pass the object, that implements the events, to one of SolFSStorage constructors that accept storageEvents parameter.
ERROR REPORTING: In Java you can't return more than one parameter, so the natural way is to throw an exception. You can throw any exception, and this exception will be passed back to the code, which called one of SolFS functions. So if you use callback mechanism and throw exception from within event handlers, be sure to wrap each call to SolFS methods with try/catch.