Transactions in a browser are more spatial (a ui component in a tree) rather than time based - a simple example is a form/object edit ui that has not been committed.
This is currently handled with "provisional transforms" (a kludge) - my original goal was "AdjunctTransformManager" - better, but still requiring custom handling of object links/refs which MVCC handles correctly, and, in the end, more simply.
A side benefit is subsequent reversion of the Job system to a single transaction model
Minor note: revisit serialization checks (still shouldn't send mvcc objects directly - the transactional objects should be populated on the client)
Transactions in a browser are more spatial (a ui component in a tree) rather than time based - a simple example is a form/object edit ui that has not been committed.
This is currently handled with "provisional transforms" (a kludge) - my original goal was "AdjunctTransformManager" - better, but still requiring custom handling of object links/refs which MVCC handles correctly, and, in the end, more simply.
A side benefit is subsequent reversion of the Job system to a single transaction model
Minor note: revisit serialization checks (still shouldn't send mvcc objects directly - the transactional objects should be populated on the client)