From 50a266dd24a1f6ff8589790b9923ef79bd1896e4 Mon Sep 17 00:00:00 2001 From: Bob Halley Date: Fri, 19 Feb 1999 01:49:31 +0000 Subject: [PATCH] update --- doc/design/database | 9 ++++----- 1 file changed, 4 insertions(+), 5 deletions(-) diff --git a/doc/design/database b/doc/design/database index 7377de1162..5552e186b1 100644 --- a/doc/design/database +++ b/doc/design/database @@ -18,11 +18,10 @@ updated by IXFR or AXFR. AXFR provides the entire contents of the new zone version, and replaces the entire contents of the database. IXFR and Dynamic Update, although completely different protocols, have the same basic database requirements. They are differential update -protocols, e.g. "add this record to the records at name 'foo'". They -are transactional, and must either succeed or fail completely. -Changes must not become visible to clients until the transaction has -committed. The differential nature of these updates requires -transaction serialization. +protocols, e.g. "add this record to the records at name 'foo'". The +updates are also atomic, i.e. they must either succeed or fail. +Changes must not become visible to clients until the update has +committed. In short, zone updates are transactional. Cache updates are done by the server in the ordinary course of handling client requests. Unlike zone updates, cache updates do not