Test markdown

dev
Philippe PITTOLI 2019-12-18 02:51:48 +01:00
parent d126abf39b
commit bd646f250d
1 changed files with 9 additions and 2 deletions

View File

@ -3,25 +3,32 @@
1. AUTHENTICATION: authentication message and informations about messages to transfer 1. AUTHENTICATION: authentication message and informations about messages to transfer
2. RESPONSE: OK or ERROR 2. RESPONSE: OK or ERROR
3. loop: 3. loop:
# TRANSFER: message id, file chunk - TRANSFER: message id, file chunk
# REPONSE: Ok - REPONSE: Ok
# messages content # messages content
format: IPC USER MESSAGE TYPE, JSON ENCODED MESSAGE format: IPC USER MESSAGE TYPE, JSON ENCODED MESSAGE
1. AUTHENTICATION message 1. AUTHENTICATION message
1, { message-id: "UUID", token: "JWT", files: [ 1, { message-id: "UUID", token: "JWT", files: [
{ name: "NAME", size: SIZE-IN-BYTES (unsigned int 64 bits) }, { name: "NAME", size: SIZE-IN-BYTES (unsigned int 64 bits) },
{ name: "NAME", size: SIZE-IN-BYTES (unsigned int 64 bits) }, { name: "NAME", size: SIZE-IN-BYTES (unsigned int 64 bits) },
], fid: "UUID", tags: [ TAG-NAME, TAG-NAME ] ], fid: "UUID", tags: [ TAG-NAME, TAG-NAME ]
} }
note: The server knows the user id from the token (JWT) and stores the received files in a note: The server knows the user id from the token (JWT) and stores the received files in a
2. RESPONSE message 2. RESPONSE message
2, { message-id: "UUID", response: "Ok" } 2, { message-id: "UUID", response: "Ok" }
or or
2, { message-id: "UUID", response: "Error", reason: "REASON" } 2, { message-id: "UUID", response: "Error", reason: "REASON" }
3. TRANSFER message 3. TRANSFER message
3, { message-id: "UUID", chunk: "UUID", data: [ BINARY DATA ] } 3, { message-id: "UUID", chunk: "UUID", data: [ BINARY DATA ] }
# Rationale # Rationale