Why Choose CBFS Connect over Dokan and Dokany?
About CBFS Connect
CBFS Connect is a software development toolkit that allows you to present various data sources as the files and directories of a local virtual drive, regardless of where the actual data is kept — be it in files, in database records, in memory, or elsewhere. CBFS Connect consists of a system-level driver and a user mode API component. You only have to write user mode code, CBFS Connect's system driver takes care of all of the lower-level hassles.
Why Use CBFS Connect?
With hundreds of clients and millions of deployments, CBFS Connect is the trusted SDK for virtualized Windows filesystems.
- Technology you can rely on: CBFS Connect is maintained by professional software developers working in a well-established business, and it is designed with reliability and business suitability in mind. CBFS Connect is maintained, supported, and regularly updated to ensure that it continues to work flawlessly with the latest versions of Windows.
- Windows-oriented architecture: Designed for Windows, CBFS Connect API is focused on the features supported by Windows (for FUSE-compatible interface, please check CBFS FUSE). With a comprehensive implementation of the Windows filesystem, CBFS Connect is the only SDK able to provide enterprise-grade solutions, from integrations with legacy applications to new applications innovating with nontraditional data sources.
Professional Products Provide Professional Reliability
CBFS Connect | Dokan | Dokany | |
---|---|---|---|
Professionally written and maintained code | |||
Many functional sample applications for all supported APIs and platforms | |||
Comprehensive documentation | |||
Timely updates and compatibility improvements | |||
Clear roadmap for future development | |||
Guaranteed support | |||
Business responsibility | |||
Cost of Ownership | Predictable and consistent | Unpredictable | Unpredictable |
Windows-Oriented Architecture Means Better Technology
CBFS Connect | Dokan(y) | |
---|---|---|
Hard links | ||
In-memory and on-disk caches | ||
Fine-grained control over user access | ||
Support for short (8.3) filenames | ||
Optional use of file Ids instead of filenames | ||
Filesystem quota support | ||
Handling of reparse points | ||
Handling of custom requests | ||
Fine-grained control over filesystem representation | ||
Control over serialization of requests | ||
Control over worker threads | ||
Custom disk icons in Explorer | ||
Plug-n-play mode with device emulation |
We appreciate your feedback. If you have any questions, comments, or suggestions about this article please contact our support team at support@callback.com.