IdAS Update Proposals Different Transactions

This is like Option 3.1, but instead of a TransactionSemantics class which is passed to update operations, we would (optionally) pass an ITransaction instance. This would allow one to build up multiple concurrent transactions (rather than only a single as Option 3.1 allows).

In absence of the ITransaction, the update would be applied immediately.

There would be some kind of ITransaction beginTransaction() method, as well as an abortTransaction(ITansaction) and commitTransaction(ITransaction) method.

The ITransaction interface could allow us to specify semantics like "ignore failures" if needed.