1. GLOMAR  Aims - Provides adaptive consistency control for mobile enabled file systems  Abstracting consistency control into a component architecture  Supply the generic framework  Provide tools for consistency control creation  Offer Transparency and Adaptation  Simplify consistency control with the generic mechanism

2. Abstracting Consistency Control  Relationship Component  Consistency Model  The Consistency Model contains the algorithms used to dictate replica maintenance  Relationship Scope  The Relationship Scope is used to specify when a Relationship Component should be implemented  Clone List  The Clone List contains the list of file this Relationship Component governs. Clone are the abstraction of files, directories, volumes and nodes.

3. Framework  Supports Relationship Components (RC)  Stores / Selects / Implements RCs  Transparent at the Application Level  Structure  The Interceptor  The System Grader  The Clone Distribution Monitor  The Remote Operation Interface  The Relationship Component Repository  The Executive

4. Local File System The System Grader The Clone Distribution Monitor The Interceptor The Relationship Component Repository The Remote Operation Interface RC1RCnRC2 Implemented RC The Executive Application RC3

5. Development Methodology  Use the RCDL (The Relationship Component Definition Language)  A declarative language that allows the:  definition of the Clone Topology  definition of the Consistency Model  definition of the Relationship Scope  definition of the binding between these three  Results in:  Consistency Model stub code (C++ Classes)  Relationship Scope stub code (C++ Classes)  Relationship Component makefile  Clone Topology in XML form  Used YooccLa to create the RCDL