bigfile: BigFile backend to store data in ZODB
This adds transactionality and with e.g. NEO allows to distribute objects to nodes into cluster. We hook into ZODB two-phase commit process as a separate data manager, and synchronize changes to memory, to changes to object only at that time. Alternative would be to get notified on every page change, and mark appropriate object as dirty right at that moment. But I wanted to stay close to filesystem design (we don't get notification for every file change from kernel) - that's why it is done the first way.  http://www.neoppod.org/
Showing with 656 additions and 0 deletions
bigfile/file_zodb.py 0 → 100644
This diff is collapsed.
bigfile/tests/__init__.py 0 → 100644
bigfile/tests/common_zodb.py 0 → 100644