Crate gix_lock

git-style registered lock files to make altering resources atomic.

In this model, reads are always atomic and can be performed directly while writes are facilitated by the locking mechanism implemented here. Locks are acquired atomically, then written to, to finally atomically overwrite the actual resource.

Lock files are wrapped gix-tempfile-handles and add the following:

• consistent naming of lock files
• block the thread (with timeout) or fail immediately if a lock cannot be obtained right away
• commit lock files to atomically put them into the location of the originally locked file

Limitations

• All limitations of gix-tempfile apply. A highlight of such a limitation is resource leakage which results in them being permanently locked unless there is user-intervention.
• As the lock file is separate from the actual resource, locking is merely a convention rather than being enforced.

Re-exports

• pub use gix_tempfile as tempfile;

Modules

• acquire
• backoff
• commit
• file

Structs

• File
  Locks a resource to eventually be overwritten with the content of this file.
• Marker
  Locks a resource to allow related resources to be updated using files.