Concurrent, Fast, Secure

Concurrently modify different files on the fly.

Fast performance through multi-threading.

Secure architecture that won't deadlock.

Simple to port to a multi-threaded environment.

Multi-Threaded From the Ground-up

FullFAT was designed from the ground-up with multi-threaded environments in mind. This means that a running process will have little impact on the performance of another concurrent process when accessing files via FullFAT.

Multi-threaded code improves the efficiency of the system overall. Using a multithreaded library like FullFAT to handle files will allow your application to be more responsive.

Secure Architecture

Because FullFAT was designed with multi-threaded environments in mind, its entire architecture has been carefully crafted to be re-entrant and safe. FullFAT uses clever constructs that prevent the developer from causing a dead-lock situation.

FullFAT expects that the underlying data I/O (block-device driver) is re-entrant. I.e. the developer must atleast protect concurrent access to the underlying device with a mutex.

Platform Independent

Thread-safety is often thought to be a platform specific feature, and one that can reduce code portability. FullFAT exposes a platform driver model, allowing the developer to provide mappings to platform specific mutex or semaphore API's.