From fcfafd3b4275994f43f5dd40624a910a681318de Mon Sep 17 00:00:00 2001 From: Brad Fitzpatrick Date: Fri, 28 Jan 2011 14:28:35 -0800 Subject: [PATCH] updated terms --- website/content/docs/terms | 32 +++++++++++++++++++++++++++++--- 1 file changed, 29 insertions(+), 3 deletions(-) diff --git a/website/content/docs/terms b/website/content/docs/terms index 6f16ddb9d..07d5ba206 100644 --- a/website/content/docs/terms +++ b/website/content/docs/terms @@ -48,10 +48,10 @@ if things here are confusing or lacking.

  • enumerate all your blobs, sorted by their blobrefs. Enumeration is - only really used by your search server and by full syncs + only really used by your search server and by a full sync between your blob server mirrors.
    • - +

    (Note: no delete operation)

    @@ -107,13 +107,22 @@ header:

    + +
    signed schema blob (aka "claim")
    + +
    if you sign a schema blob, + it's now a "signed schema blob" or "claim". The terms are used pretty + interchangably but generally it's called a claim when the target of + the schema blob is an object's permanode (see below). + +
    object
    something that's mutable. While a blob is a single - immutable thing, an object is a collection of schema blobs + immutable thing, an object is a collection of claims which mutate an object over time. See permanode for fuller discussion.
    @@ -148,6 +157,23 @@ header:

    + +
    full sync
    +
    synchronizing all your blobs between two or more of your blob servers +(e.g. mirroring between your house, App Engine, and Amazon). + +

    Generally a full sync will be done with the blob server's enumerate +support and no knowledge of the schema. It's a dumb copy of all blobs that the +other party doesn't already have.

    +
    + + +
    graph sync
    + +
    as opposed to a full sync, a graph sync is synchronizing +a sub-graph of your blobs between blob servers. This level of sync will operate +with knowledge of the schema.
    +
    search server
    indexer