Returns this replica's version.
Sets the replica's version to the given integer.
Return the replica's UUID
Returns an ordered set of changeset objects for all changesets containing changes to this object.
Note that changesets may include changes to other records
If "limit" is specified, only returns that many changesets (starting from record creation).
Creates a new Prophet::ChangeSet, which new changes will be added to.
$URL /<db-uuid>/ /replica-uuid /latest-sequence-no /replica-version /cas/records/<substr(sha1,0,1)>/substr(sha1,1,1)/<sha1> /cas/changesets/<substr(sha1,0,1)>/substr(sha1,1,1)/<sha1> /records (optional?) /<record type> (for resolution is actually _prophet-resolution-<cas-key>) /<record uuid> which is a file containing a list of 0 or more rows last-changed-sequence-no : cas key /changesets.idx index which has records: each record is : local-replica-seq-no : original-uuid : original-seq-no : cas key ... /resolutions/ /replica-uuid /latest-sequence-no /cas/<substr(sha1,0,1)>/substr(sha1,1,1)/<sha1> /content (optional?) /_prophet-resolution-<cas-key> (cas-key == a hash the conflicting change) /<record uuid> (record uuid == the originating replica) last-changed-sequence-no : <cas key to the content of the resolution> /changesets.idx index which has records: each record is : local-replica-seq-no : original-uuid : original-seq-no : cas key ...
Inside the top level directory for the mirror, you'll find a directory named as a hex-encoded UUID. This directory is the root of the published replica. The uuid uniquely identifes the database being replicated. All replicas of this database will share the same UUID.
Inside the <db-uuid> directory, are a set of files and directories that make up the actual content of the database replica:
Contains the replica's hex-encoded UUID.
Contains a single integer that defines the replica format.
The current replica version is 1.
Contains a single integer, the replica's most recent sequence number.
cas directory holds changesets and records, each keyed by a hex-encoded hash of the item's content. Inside the
cas directory, you'll find a two-level deep directory tree of single-character hex digits. You'll find the changeset with the sha1 digest
You'll find the record with the sha1 digest
TODO: define the format for changesets and records
Files inside the
records directory are index files which list off all published versions of a record and the key necessary to retrieve the record from the content-addressed store.
records directory, you'll find directories named for each
type in your database. Inside each
type directory, you'll find a two-level directory tree of single hexadecimal digits. You'll find the record with the type <Foo> and the UUID
29A3CA16-03C5-11DD-9AE0-E25CFCEE7EC4 stored in
The format of record files is:
<unsigned-long-int: last-changed-sequence-no><40 chars of hex: cas key>
The file is sorted in asecnding order by revision id.
changesets.idx file lists each changeset in this replica and provides an index into the content-addressed storage to fetch the content of the changeset.
The format of record files is:
<unsigned-long-int: sequence-no><16 bytes: changeset original source uuid><unsigned-long-int: changeset original source sequence no><16 bytes: cas key - sha1 sum of the changeset's content>
The file is sorted in ascending order by revision id.
This software is Copyright (c) 2009 by Best Practical Solutions.
This is free software, licensed under:
The MIT (X11) License
You can make new bug reports, and view existing ones, through the web interface at https://rt.cpan.org/Public/Dist/Display.html?Name=Prophet.