Comment Actions
We'll want to be able to wrap multiple modifications into a transaction, which may translate to storage level transactions, but mostly makes sure that:
- All modifications of that transaction are processed immediately, without being interleaved with modifications from the source.
- If one modification fails, all modifications are dropped
- The whole transaction becomes visible to the rest of they system as one (which probably means using storage level transactions, or marking entities as not yet public)
Comment Actions
The usecases for this are:
- client or synchronizer wanting transaction semantics
- A modification that has a non 1:1 entity-buffer mapping grouping the related modifications.