How does AutoTMF know when to end a transaction?
AutoTMF has a complex set of processing rules to manage transactions. The are two basic rules: • All automatic transactions must be committed; no updates should ever be rolled back due to transaction abort. • All locking protocols should be observed. No record or file lock should be released by an automatic transaction commit unless the application has unlocked the records or file. Given these “rules,” AutoTMF has a number of strategies to decide when to commit transactions. It normally assumes that each server request is a single transaction. It also tries to balance efficiency (i.e., using a single transaction for many updates) and concurrency (not keeping records locked by a long-running transaction). Finally, it respects the need for isolation to avoid lock contention between cooperating processes.
