perso/syncthing-arm
1
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity

Further clarify message ordering requirements (ref #377)

Browse Source
This commit is contained in:
Jakob Borg 2014-06-19 01:59:58 +02:00
parent de75550415
commit 0e59b5678a
1 changed files with 11 additions and 10 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

21
protocol/PROTOCOL.md
View File

@ -59,11 +59,11 @@ or certificate pinning combined with some out of band first
verification. The reference implementation uses preshared certificate verification. The reference implementation uses preshared certificate
fingerprints (SHA-256) referred to as "Node IDs". fingerprints (SHA-256) referred to as "Node IDs".
There is no required order or synchronization among BEP messages (except There is no required order or synchronization among BEP messages except
for the requirements on Cluster Config messages below) - any message as noted per message type - any message type may be sent at any time and
type may be sent at any time and the sender need not await a response to the sender need not await a response to one message before sending
one message before sending another. Responses MUST however be sent in another. Responses MUST however be sent in the same order as the
the same order as the requests are received. requests are received.
The underlying transport protocol MUST be TCP. The underlying transport protocol MUST be TCP.
@ -297,11 +297,12 @@ peers acting in a specific manner as a result of sent options.
### Index (Type = 1) ### Index (Type = 1)
The Index message defines the contents of the senders repository. An The Index message defines the contents of the senders repository. An
Index message MUST be sent by each node immediately upon connection. A Index message MUST be sent for each repository mentioned in the Cluster
node with no data to advertise MUST send an empty Index message (a file Config message. An Index message for a repository MUST be sent before
list of zero length). If the repository contents change from non-empty any other message referring to that repository. A node with no data to
to empty, an empty Index message MUST be sent. There is no response to advertise MUST send an empty Index message (a file list of zero length).
the Index message. If the repository contents change from non-empty to empty, an empty
Index message MUST be sent. There is no response to the Index message.
#### Graphical Representation #### Graphical Representation