Show More
@@ -0,0 +1,28 b'' | |||
|
1 | # INTRO # | |
|
2 | ||
|
3 | This document discribes the server sync protocol. | |
|
4 | ||
|
5 | # DRAFT PROTOCOL DESCRIPTION # | |
|
6 | ||
|
7 | Version: | |
|
8 | * Protocol version | |
|
9 | * Model version | |
|
10 | ||
|
11 | Node data: | |
|
12 | * Public key | |
|
13 | ||
|
14 | Object data: | |
|
15 | * Post | |
|
16 | * Post list (for sync) | |
|
17 | ||
|
18 | The node requests other node's changes list since some time (since epoch if | |
|
19 | this is the start). The other node sends a list of post ids or posts in the | |
|
20 | XML or JSON format. | |
|
21 | ||
|
22 | Protocol version is the version of the sync api. Model version is the version | |
|
23 | of data models. If at least one of them is different, the sync cannot be | |
|
24 | performed. | |
|
25 | ||
|
26 | The node signs the data with its key. The receiving node saves the key at the | |
|
27 | first sync and checks it every time. If the key has changed, the info won't be | |
|
28 | saved from the node (or the node id must be changed). |
General Comments 0
You need to be logged in to leave comments.
Login now