Callback File System 2.0.34

Callback File System lets you implement your own file system in Windows


File System driver creates a virtual device with application-provided file system and emulates a physical storage.
The driver works on the system level and turns a storage into a "real" disk device with its own file system. The "real disk device" is accessible in read-only and/or read-write mode by any application which uses system file management API.

The driver lets you make the mounted disk visible to the user or hide it from the user.
Unlike CallbackDisk, the driver of Callback File System provides a functionality to create not just your virtual disks, but your own file systems. The driver provides a callback mechanism, which lets you keep your files and file systems wherever you want (i.e. on remote computer, in memory or database tables etc.).

User-mode API
User-mode API is simple and introduces about ten functions, specific to driver management and storage mounting operations. Also the API includes about 20 callback functions (events) which your application must handle to effectively represent a full-featured file system.
The API is needed only for driver and storage manipulation. All file operations can be performed using system file management API or framework-specific classes.

User-mode API is provided as a .NET component for .NET Framework development, a static library with one class for use in C++ and a VCL component for use in Delphi.

Security Features
Callback File System supports various security features. First of all, you can expose the virtual disk to the user by assigning it a drive letter, or you can keep the virtual disk hidden from users eye (when no drive letter is assigned). Next, Callback File System lets you control what applications or users access the data. Finally, you can support NTFS security functions for files and directories stored within Callback File System.