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