octoleo/syncthing
1
0
Fork 0
mirror of https://github.com/octoleo/syncthing.git synced 2025-01-24 07:28:27 +00:00
Code Issues Packages Projects Releases Wiki Activity

Merge pull request #537 from marclaporte/patch-2

Browse Source 
Fix some typos
This commit is contained in:
Jakob Borg 2014-08-18 10:43:29 +02:00
commit 2f055a75a0
1 changed files with 4 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
protocol/PROTOCOL.md
View File

@ -9,7 +9,7 @@ node has one or more _repositories_ of files described by the _local
model_, containing metadata and block hashes. The local model is sent to model_, containing metadata and block hashes. The local model is sent to
the other nodes in the cluster. The union of all files in the local the other nodes in the cluster. The union of all files in the local
models, with files selected for highest change version, forms the models, with files selected for highest change version, forms the
_global model_. Each node strives to get it's repositories in sync with _global model_. Each node strives to get its repositories in sync with
the global model by requesting missing or outdated blocks from the other the global model by requesting missing or outdated blocks from the other
nodes in the cluster. nodes in the cluster.
@ -111,7 +111,7 @@ For C=0:
* The message is not compressed. * The message is not compressed.
All data within the the message (post decompression, if compression is All data within the message (post decompression, if compression is
in use) MUST be in XDR (RFC 1014) encoding. All fields shorter than 32 in use) MUST be in XDR (RFC 1014) encoding. All fields shorter than 32
bits and all variable length data MUST be padded to a multiple of 32 bits and all variable length data MUST be padded to a multiple of 32
bits. The actual data types in use by BEP, in XDR naming convention, are bits. The actual data types in use by BEP, in XDR naming convention, are
@ -624,8 +624,8 @@ directions.
### Read Only ### Read Only
In read only mode a node does not synchronize the local repository to In read only mode, a node does not synchronize the local repository to
the cluster, but publishes changes to it's local repository contents as the cluster, but publishes changes to its local repository contents as
usual. The local repository can be seen as a "master copy" that is never usual. The local repository can be seen as a "master copy" that is never
affected by the actions of other cluster nodes. affected by the actions of other cluster nodes.