Construct a FileBucket with the provided path, record-size, and inital record count. The latter causes records to be pre-allocated, saving a certain amount of growth activity. Selecting a record size that roughly matches the serialized content will limit 'thrashing'.
Close this FileBucket -- all content is lost.
Return the serialized data for the provided key. Returns null if the key was not found.
Return the block-size in use for this FileBucket
Return where the FileBucket is located
Return the currently populated size of this FileBucket
Write a serialized block of data, and associate it with the provided key. All keys must be unique, and it is the responsibility of the programmer to ensure this. Reusing an existing key will overwrite previous data.
Remove the provided key from this FileBucket.
Define the capacity (block-size) of each record
FileBucket implements a simple mechanism to store and recover a large quantity of data for the duration of the hosting process. It is intended to act as a local-cache for a remote data-source, or as a spillover area for large in-memory cache instances.
Note that any and all stored data is rendered invalid the moment a FileBucket object is garbage-collected.
The implementation follows a fixed-capacity record scheme, where content can be rewritten in-place until said capacity is reached. At such time, the altered content is moved to a larger capacity record at end-of-file, and a hole remains at the prior location. These holes are not collected, since the lifespan of a FileBucket is limited to that of the host process.
All index keys must be unique. Writing to the FileBucket with an existing key will overwrite any previous content. What follows is a contrived example: