| |
| | ONJava.com -- Atomic File Transactions, Part 1 |
 | | Atomicity is crucial for writing correct software in many applications; for example, a bank's software may implement a transfer from account A to account B as a withdrawal from A followed by a deposit to B. If the first action happens, then the second had better happen as well. |
 | | In standard parlance, a transaction is a sequence of operations with four properties, called the ACID properties, for Atomicity, Consistency, Isolation, and Durability. |
 | | Atomicity means that a transaction can end in only one of two ways: either successfully, in which case all its effects take place, or unsuccessfully, in which case it has no effect -- for all intents and purposes, the transaction never happened. |
| www.onjava.com /pub/a/onjava/2001/11/07/atomic.html (1126 words) |
|