Difference between revisions of "Deployment Platform/Sneakernet/Packets format"
Jump to navigation
Jump to search
| Line 31: | Line 31: | ||
:* {{Code|pull_sequence}}: Sequence after merging original PUSH packet | :* {{Code|pull_sequence}}: Sequence after merging original PUSH packet | ||
| − | * ''' | + | * '''sn_pull''', pull Sugar Network data. |
| − | :* {{Code| | + | :* {{Code|cmd: sn_pull}}; |
| − | :* {{Code| | + | :* {{Code|sequence}}: sequence to pull. |
| − | :* {{Code| | + | |
| − | :* {{Code|sequence}} | + | * '''files_pull''', pull files from shared directory. |
| + | :* {{Code|cmd: files_pull}}; | ||
| + | :* {{Code|directory}}, synchronized directory to pull; | ||
| + | :* {{Code|sequence}}, sequence to pull. | ||
Revision as of 10:57, 27 July 2012
Packets format
Packets are tarball files with .packet suffix.
On logic level, every packet consists of:
- one header, a dictionary of key-value pairs;
- records, a dictionary of key-value pairs and optional data depending on record type.
Header
Header is being stored in JSON notation in /header file in packet tarball.
src, sender's GUIDdst, optional destination GUIDfilename, suggested file name for packet file, it is assumed to be unique
Record types
- sn_push:
cmd:sn_pushsrc: sender's identity to push from[dst]: receiver's identity to push to, optional for packets from mastersequence: Sequence associated with packet's payload
- ACK packet:
type:acksrc: master's identitydst: receiver's identity ack is intended forpush_sequence: original PUSH packet's sequencepull_sequence: Sequence after merging original PUSH packet
- sn_pull, pull Sugar Network data.
cmd: sn_pull;sequence: sequence to pull.
- files_pull, pull files from shared directory.
cmd: files_pull;directory, synchronized directory to pull;sequence, sequence to pull.