Jul 3, 2024

After some thinking on this it appears that I can most easily and cleanly implement a block/tx object targeted allocator using a new constructor on the fast io streams that we use to construct all objects from the network and store. By defining an interface and optionally accepting an instance on reader construct, the reader can hold and provide the common allocator. It can also provide a shared lock object that allows for reset of the mmap when full, by blocking and waiting until all objects are cleared. Of course these cannot be long-lived objects, or they cause a deadlock. This is the same pattern used by the store presently.