b2f:bcf_v1
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
b2f:bcf_v1 [2025/02/14 14:34] – [Binary Compressed Forward Version 1] f4hof | b2f:bcf_v1 [2025/02/14 15:03] (current) – [Transfer Mode] f4hof | ||
---|---|---|---|
Line 1: | Line 1: | ||
====== Binary Compressed Forward Version 1 ====== | ====== Binary Compressed Forward Version 1 ====== | ||
- | This version of the protocol is an extension to both the [[b2f: | + | This protocol |
This version is advertised in the SID Features field with the '' | This version is advertised in the SID Features field with the '' | ||
Line 10: | Line 10: | ||
* An enlarged set of selective retrieval replies. | * An enlarged set of selective retrieval replies. | ||
* The first transmitted block structure is slightly changed | * The first transmitted block structure is slightly changed | ||
- | | + | |
+ | The Binary Compressed Forward protocol MUST operate over a [[https:// | ||
===== Commands ===== | ===== Commands ===== | ||
Line 25: | Line 26: | ||
===== Transfer Mode ===== | ===== Transfer Mode ===== | ||
+ | |||
+ | Each transfer is equivalent to the transfer of one message of the standard protocol. It SHALL NOT be followed by the '' | ||
+ | |||
+ | The first transmitted data block MUST contain the full binary file's CRC16 checksum, the full uncompressed file size as a 32 bit little-endian integer, and the binary content of the file, starting from the start of the file, or from the requested offset, depending on the decision transmitted through the selective retrieval command. | ||
+ | |||
+ | In case of a checksum error, the message or the file MUST NOT be considered as transmitted. The system MUST send the comment, then issue a disconnect request. | ||
+ | |||
+ | < | ||
+ | |||
+ | |||
< | < |
b2f/bcf_v1.1739543679.txt.gz · Last modified: 2025/02/14 14:34 by f4hof