[Ur] Generalizing transactions

[Karn Kallio]

Adam, now that somebody ( Marc Weber ) is working on an application ( payment 
gateway ) where the transaction model of Ur/Web does not cleanly apply, is 
there a chance of you generalizing Ur/Web transactions in a safe, principled 
way ( that allows representing the semantics of the application's effectful 
operations within Ur/Web )?  For example, I think that the problem of leaving 
a permanent record of an event ( e.g. receiving an order and not removing it 
on failure rollback ) could be handled with a SAGA that has a null 
compensation for the process of writing the record.