... | @@ -42,7 +42,7 @@ A CHUNK request contains a chunk of a previously *offered* file. *Note: Since th |
... | @@ -42,7 +42,7 @@ A CHUNK request contains a chunk of a previously *offered* file. *Note: Since th |
|
+ **CHUNK:** *[BDF raw]* chunk
|
|
+ **CHUNK:** *[BDF raw]* chunk
|
|
|
|
|
|
+ **RESPONSE:** yes (Functions as ACK)
|
|
+ **RESPONSE:** yes (Functions as ACK)
|
|
+ **BODY:** ``null`
|
|
+ **BODY:** `null`
|
|
|
|
|
|
### CHUNK_FIN
|
|
### CHUNK_FIN
|
|
A CHUNK_FIN request indicates that the last ACK for the given file id's chunk requests has been received. The recipient is then able to confidently delete the file. *NOTE: Without the CHUNK_FIN request a file could theoretically be resent if the last ACK request is lost.*
|
|
A CHUNK_FIN request indicates that the last ACK for the given file id's chunk requests has been received. The recipient is then able to confidently delete the file. *NOTE: Without the CHUNK_FIN request a file could theoretically be resent if the last ACK request is lost.*
|
... | @@ -55,14 +55,14 @@ A CHUNK_FIN request indicates that the last ACK for the given file id's chunk re |
... | @@ -55,14 +55,14 @@ A CHUNK_FIN request indicates that the last ACK for the given file id's chunk re |
|
### SYNC
|
|
### SYNC
|
|
SYNC requests are used to carry [BSP](https://code.briarproject.org/briar/briar-spec/blob/master/protocols/BSP.md) messages between the mailbox and the connected client.
|
|
SYNC requests are used to carry [BSP](https://code.briarproject.org/briar/briar-spec/blob/master/protocols/BSP.md) messages between the mailbox and the connected client.
|
|
|
|
|
|
+ **RESPONSE:** no
|
|
|
|
|
|
|
|
+ **BODY:** [STREAM]
|
|
+ **BODY:** [STREAM]
|
|
+ **STREAM:** *[BDF raw/null]* Either bytes containing a collection of [BSP](https://code.briarproject.org/briar/briar-spec/blob/master/protocols/BSP.md) messages or `null` to indicate an "end of stream"
|
|
+ **STREAM:** *[BDF raw/null]* Either bytes containing a collection of [BSP](https://code.briarproject.org/briar/briar-spec/blob/master/protocols/BSP.md) messages or `null` to indicate an "end of stream"
|
|
|
|
|
|
|
|
+ **RESPONSE:** no
|
|
|
|
|
|
### END
|
|
### END
|
|
The END request indicates that the sending peer does not have any messages left to send and wishes to close the connection. If both peers have received an END request, the connection can be closed.
|
|
The END request indicates that the sending peer does not have any messages left to send and wishes to close the connection. If both peers have received an END request, the connection can be closed.
|
|
|
|
|
|
+ **RESPONSE:** no
|
|
+ **BODY:** No elements
|
|
+ **BODY:** No elements |
|
|
|
\ No newline at end of file |
|
+ **RESPONSE:** no |
|
|
|
\ No newline at end of file |