ieb/sparsemapcontent — Issue #146: Investigate transactions
Author: ieb
Created: 2011-12-15 07:16:02+00:00
State: open

The code base does not perform session bound transactions at present. We have a reasonably efficient redo log that would enable each session to manage a commit state in memory. At the end of the transactional cycle the redo log could be played back to the underlying storage in a packet, effectively committing the changes in order. Thats one way of addressing this. The other way that could be considered is to maintain a image of transaction state in the session, as a session bound write through cache. On commit the cache gets committed to storage. This approach will not maintain the order of operations on the cache, but will ensure that the number of operations being performed is minimised. Minimising the number of operations will be a good thing, however loosing the order of oprations might cause issues for any async listeners attached to the session. There needs to be some definition an clarification here.