Cancellation and wc-ng txns

What's the relationship between cancellation functions and
transactions in wc-ng?

In the interests of performance and correctness, we've been moving
toward a model where more and more gets done in a single wc-ng
transaction. I've no problem with that, and like the atomicity and
speed it gives us, but how does that interact with our cancellation
functions? Do we still check for cancellation from within the
transaction? If the user cancels, do we rollback the transaction, or
commit it?

My question then is two-fold:
 * what actually happens today?
 * and what is the Right Thing to happen?

My own thoughts: we should check for cancellation, and if it occurs,
we should rollback the txn.

-Hyrum
Received on 2011-04-22 23:11:56 CEST