Technical Specification

Description

Callback File System is a component set for presentation of data as files and directories of a local virtual disk. Regardless of where the actual data are kept: in files, in database records, memory, or elsewhere - they will be treated as if they were parts of a single file system.

Callback File System consists of the system-level driver and user-mode API.

Driver

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 used for driver and storage manipulation and for security operations. All file operations can be performed using system file management API or framework-specific classes.

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 user's 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.

Miss a feature? Tell us about your idea using Wish List.

Supported platforms

• Windows:
  • Windows 2008 Server R2 (32-bit, 64-bit AMD64 and 64-bit Itanium)
  • Windows 7 (32-bit, 64-bit AMD64 and 64-bit Itanium)
  • Windows 2008 Server (32-bit, 64-bit AMD64 and 64-bit Itanium)
  • Windows Vista (32-bit, 64-bit AMD64 and 64-bit Itanium)
  • Windows 2003 Server (32-bit, 64-bit AMD64 and 64-bit Itanium)
  • Windows XP (32-bit, 64-bit AMD64 and 64-bit Itanium)
• Microsoft .NET Framework on Windows:
  • .NET 4.0 (32-bit, 64-bit x64 and Itanium)
  • .NET 3.5 (32-bit, 64-bit x64 and Itanium)
  • .NET 3.0 (32-bit, 64-bit x64 and Itanium)
  • .NET 2.0 (32-bit, 64-bit x64 and Itanium)
  • .NET 1.1

Development tools

• .NET API:
  • Visual Studio 2010
  • Visual Studio 2008
  • Visual Studio 2005
  • Visual Studio.NET 2003
  • CodeGear Prism
  • CodeGear RAD Studio 2007
  • Delphi 2007
  • Delphi 2006
  • Delphi 2005
• C++ API:
  • Visual Studio 2010
  • Visual Studio 2008
  • Visual Studio 2005
  • Visual Studio.NET 2003
  • Visual Studio 6 / Visual C++ 6
  • CodeGear RAD Studio 2010
  • CodeGear RAD Studio 2009
  • CodeGear RAD Studio 2007
  • C++Builder 2010
  • C++Builder 2009
  • C++Builder 2007
  • C++Builder 6
  • C++Builder 5
  • C++Builder 4
• VCL API (VCL units are linked into the application without any external DLLs):
  • CodeGear RAD Studio 2010
  • CodeGear RAD Studio 2009
  • CodeGear RAD Studio 2007
  • Delphi 2010
  • Delphi 2009
  • Delphi 2007
  • Delphi 2006
  • Delphi 2005
  • Delphi 7
  • Delphi 6
  • Delphi 5
  • C++Builder 2010
  • C++Builder 2009
  • C++Builder 2007
  • C++Builder 6
  • C++Builder 5
  • C++Builder 4

Miss a feature? Tell us about your idea using Wish List.

To request more details please use our feedback form or Web-based Helpdesk system.

Ready to try? Download your own copy to try Callback File System for free. Ready to pull the trigger? Refer to the Prices and Ordering page for complete licensing information.