[December 31, 2001] Described in two IETF Internet Draft documents, the ANTACID Replication Service specifies a protocol and algorithms "designed to replicate hierarchically named repositories of XML documents for business-critical, internetworked applications." The protocol is defined in terms of a BEEP profile. XML DTDs are presented in appendices of the 'Protocol and Algorithms' document.
[December 31, 2001] "The ANTACID Replication Service: Rationale and Architecture." By Michael F. Schwartz [WWW]. IETF Network Working Group, Internet-Draft. Reference: 'draft-schwartz-antacid-service-00'. Date: October 7, 2001, Expires: April 7, 2002. See also the preceding entry. ['This memo presents the ANTACID Replication Service, which replicates hierarchically named repositories of XML documents for business- critical, internetworked applications.'] "In this document we present the motivation, design rationale, and architecture for the ANTACID Replication Service (ARS). ARS replicates repositories of hierarchically-named, well-formed XML documents in a manner that supports business-critical, internetworked applications (BCIAs). The ARS protocol and algorithmic details are defined in a companion document. By 'business-critical' we mean applications requiring stronger data coherence guarantees than file-by-file replication, but weaker than global ACID semantics (i.e., Atomic, Consistent, Isolated, Durable semantics spanning all replicas). Our motivation is that many commercial services require coherence guarantees for replicated data, but that global ACID semantics are not appropriate across the Internet because: (1) global ACID semantics don't scale (a point we will discuss in more depth later); and (2) applications requiring global ACID semantics (e.g., banking) often require privately owned, centrally controlled infrastructure rather than the open Internet. The 'ANTACID' part of ARS refers to data coherence semantics we define later in this document, which we believe are well suited to BCIAs... The current effort seeks to define a standard capable of replicating data for use by BCIA's, allowing a robust service to be deployed by configuration rather than custom development/integration. The current effort also seeks to incorporate lessons learned over the past 20 years from both the RDBMS and the IETF worlds. Both the protocol and the data units replicated by ARS are XML-based because we're betting on XML to become a dominant means of structuring data on the Internet..." [cache, alt URL]
[December 31, 2001] "The ANTACID Replication Service: Protocol and Algorithms." By Michael F. Schwartz [WWW]. IETF Network Working Group, Internet-Draft. Reference: draft-schwartz-antacid-protocol-00. Date: October 7, 2001, Expires: April 7, 2002. See the following bibliographic item for the ARS Rationale and Architecture. ['This memo specifies the protocol and algorithms of the ANTACID Replication Service, designed to replicate hierarchically named repositories of XML documents for business-critical, internetworked applications.'] "This document specifies the protocol and algorithms used to implement the ANTACID Replication Service (ARS). Readers are referred to "The ANTACID Replication Service: Rationale and Architecture" [IETF 'draft-schwartz-antacid-service-00'] for a motivation of the problem addressed, the replication architecture, and terminology used in the current document. The current document assumes the reader has already read that document, and that the reader is familiar with XML. Moreover, since the ARS protocol is defined in terms of a BEEP profile, readers are referred to that document for background... We begin in Section 2 by walking through example ARS interactions, to give the reader a concrete flavor for how the protocol works. We then (Section 3) present the ARS syntax and semantics, and then provide algorithms and implementation details..." See the XML DTDs from Appendices D - I. See also: "Blocks eXtensible eXchange Protocol Framework (BEEP)." [cache, alt URL]
References:
- "The ANTACID Replication Service: Rationale and Architecture."
- "The ANTACID Replication Service: Protocol and Algorithms."
- XML DTDs from 'Protocol and Algorithms', Appendices D - I.
- See also: "Blocks eXtensible eXchange Protocol Framework (BEEP)."
