[Bps-public-commit] r11024 - SVN-PropDB

[jesse at bestpractical.com]

Author: jesse
Date: Fri Mar  7 12:54:44 2008
New Revision: 11024

Modified:
   SVN-PropDB/   (props changed)
   SVN-PropDB/notes

Log:
 r28176 at 31b:  jesse | 2008-03-07 12:50:21 -0500
 * removed glossary from notes


Modified: SVN-PropDB/notes
==============================================================================
--- SVN-PropDB/notes	(original)
+++ SVN-PropDB/notes	Fri Mar  7 12:54:44 2008
@@ -12,49 +12,9 @@
    8. The network is homogeneous.
 
 
-nihao
 
-Glossary:
+Notes on conflict
 
-
-Database
-    A term to describe a uniquely identified set of object types and records sharing a single 'base' revision and Replica identifier
-    A database contains multiple Records
-    
-Replica
-    An instance of a database. Replicas are expected to contain all Changesets from any other replica they have been synchronized with, but those Changesets are not guaranteed to be in the same sequence on each replica
-    
-Changeset
-    A changeset contains "old" and "new" versions of a set of database "Records", they can be of any Record Type.
-
-Change
-    An entry in a changeset. Contains all the updates to a given record for this changeset
-   
-Record
-    A Record is composed of zero or more Attributes and a universally unique identifier. Each record is categorized into a Record Type.
-        
-    (Discussion:    Really? I was just storing them under different dirs in the database. the goal was to provide a little separation between different kinds of nodes for managability.
-
-(ah fine. then need to forget about changing types ;)    
-indeed. 
-
-
-Record Type 
-    A Record Type is a category or "bucket" for zero or more records applications may define specific behaviours for Records of a certain Record Type, but Prophet does no more than to tag Records with a Record Type.
-Record Types are uniquely identified with a textual name and a UUID
-    
-    
-
-Attribute
-    A key-value pair on a Record.    
-
-Conflict
-    A Conflict occurs when synchronizing Replica A to B, if different Changesets have been applied to both replicas
-    
-    when the "old" version in the changeset doens't match the value of the record in the target replica?  changeset X: record alpha key FOO, old => BAR, new => ORZ from A.  If B has record alpha key FOO being BAR => applied cleanly
-    
-    
-    
     Initial state:
     
     clkao: record 1.   foo: bar (clkao at 1)