At present, the cache-locking mechanism limits access to one file at a time. This prevents a cache invalidation from causing errors to a previously-acquired cached file, but at the cost of total serialization of all file access. A more sophisticated approach to
cache invalidation (e.g., managing an "in-use" flag per cached item) would provide for greater concurrency.
At present, the cache-locking mechanism limits access to one file at a time. This prevents a cache invalidation from causing errors to a previously-acquired cached file, but at the cost of total serialization of all file access. A more sophisticated approach to
cache invalidation (e.g., managing an "in-use" flag per cached item) would provide for greater concurrency.