Connected: An Internet Encyclopedia
3.7. Atomicity

Up: Connected: An Internet Encyclopedia
Up: Requests For Comments
Up: RFC 2136
Up: 3. Server Behavior
Prev: 3.6. Zone Identity
Next: 3.8. Response

3.7. Atomicity

3.7. Atomicity

During the processing of an UPDATE transaction, the server must ensure atomicity with respect to other (concurrent) UPDATE or QUERY transactions. No two transactions can be processed concurrently if either depends on the final results of the other; in particular, a QUERY should not be able to retrieve RRsets which have been partially modified by a concurrent UPDATE, and an UPDATE should not be able to start from prerequisites that might not still hold at the completion of some other concurrent UPDATE. Finally, if two UPDATE transactions would modify the same names, RRs or RRsets, then such UPDATE transactions must be serialized.


Next: 3.8. Response

Connected: An Internet Encyclopedia
3.7. Atomicity