Introduction

Welcome to CBFS Sync, a suite of classes enabling seamless synchronization between local files and cloud storages or other remote repositories.

Add OneDrive-style, bidirectional synchronization to your applications with CBFS Sync. The event-driven design of CBFS Sync provides an intuitive way to handle operations performed on local files and folders. When remote changes are made, use the included methods to notify the local system.

The CBSync class builds on industry-standard technologies, including the Cloud Filter API on Windows, FUSE on Linux, and File Provider on macOS. CBSync reduces development time and improves the user experience by providing a single API. All icons and indicators visible to the user are presented by the operating system, ensuring a native experience.

The choice of the remote storage is entirely up to you. Whether your data are stored on a popular cloud storage service, a custom file server, or anywhere else, CBFS Sync provides a simple API to facilitate synchronization. CBFS Sync handles integration with the OS, while your code is responsible for handling events and transferring data between local and remote systems. Because your code interacts with the backend, you can also decide to make the synchronization one-way or bidirectional.

Included Classes

Additional Information

You will always find the latest information about CBFS Sync at our web site: www.callback.com. We offer free, fully-functional 30-day trials for all of our products, and our technical support staff are happy to answer any questions you may have during your evaluation.

Please direct all technical questions to support@callback.com. To help support technicians assist you as quickly as possible, please provide a detailed and accurate description of your problem, the results you expected, and the results that you received while using our product. For questions about licensing and pricing, and all other general inquiries, please contact sales@callback.com.

Thank You!

Thank you for choosing CBFS Sync for your development needs. We realize that you have a choice among development tools, and that by choosing us you are counting on us to be a key component in your business. We work around the clock to provide you with ongoing enhancements, support, and innovative products; and we will always do our best to exceed your expectations!

Deployment

The user-mode library comes in two pieces, both of which must be deployed along with the application:

1. A JAR file, named cbfssync.jar
2. A platform-native dynamic library with JNI (Java Native Interface), named as follows:
   • Windows: jnicbfssync24.dll (available for 32-bit (x86) and 64-bit (x64) processors)
   • Linux: libjnicbfssync.24.0.so (available for 32-bit (x86) and 64-bit (x64) processors)
   • macOS: libjnicbfssync24.0.dylib (available for x64 and ARM64 processors)

When deploying the application, copy both the JAR and the native library to the target system and place them next to the application.

Alternatively, the native dynamic library may be placed into one of directories, the paths to which are contained in the

• Windows: PATH environment variable, such as C:\Windows\System32 (or C:\Windows\SysWOW64 when deploying a 32-bit application on a 64-bit Windows system)
• Linux: LD_LIBRARY_PATH environment variable
• macOS: DYLD_LIBRARY_PATH environment variable

Note: A deploy.jar file also may be used instead of cbfssync.jar; it is smaller, and does not contain Intellisense data or Javadoc content.

Windows:

The native library may alternatively be installed to the Windows system directory. This approach allows deploying both the 32-bit and 64-bit versions of the native library simultaneously, because each gets placed into the system directory that corresponds to the appropriate processor architecture.

Constants