I've thought about it a lot. Since this "optimization" normally destroys the
integrity of transactions, I decided not to implement it the usual way. You
can maintain transactional integrity if the last resource is also used as the
transaction log and the transaction log "prepare" entries are i
Hi,
Has there been any thought of implementing the so-called "last
resource commit optimization" in TransactionImpl.internalPrepare?
The idea is, on the last resource in the list, to avoid calling
prepare() and immediately call commit(onePhase=true). Deciding when
and which resource to put last in
