aborts: too high a cost

When the cost of an abort is high, then commands needs must be fully validated prior to entering the transactional context, adding to the complexity of the application. I'd rather keep the cost of aborting a transaction low, thus reducing the risk of application errors by minimizing application complexity.

However, I had not considered the impact of an abort on a cache until late in the game. So I want to go back and make the caches transactional participants, rather than taking a heavy handed approach at a higher level.

Bill