b2f:bcf_v0
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
b2f:bcf_v0 [2025/02/14 10:43] – [Commands] f4hof | b2f:bcf_v0 [2025/02/14 10:45] (current) – [Binary File Transfer Mode] f4hof | ||
---|---|---|---|
Line 24: | Line 24: | ||
==== Pending Binary File Proposal ==== | ==== Pending Binary File Proposal ==== | ||
- | ===== Transfer | + | ===== Transfer |
The message/ | The message/ | ||
Line 31: | Line 31: | ||
Unlike YAPP transfers, there is no individual packet acknowledgement during the transmission of messages. The protocol is thus simpler and more efficient. | Unlike YAPP transfers, there is no individual packet acknowledgement during the transmission of messages. The protocol is thus simpler and more efficient. | ||
- | ==== ASCII Message Transfer | + | |
+ | As with the underlying protocol, the channel direction is immediately reversed after the completion of a transfer batch. | ||
+ | ==== ASCII Message Transfer | ||
FIXME proposal format definition | FIXME proposal format definition | ||
Line 52: | Line 54: | ||
Security considerations: | Security considerations: | ||
* If you're using a memory-unsafe language, you SHOULD pay extra care with the attribute size field to avoid buffer overflow attacks. | * If you're using a memory-unsafe language, you SHOULD pay extra care with the attribute size field to avoid buffer overflow attacks. | ||
- | ==== Binary File Transfer | + | ==== Binary File Transfer |
FIXME proposal format definition | FIXME proposal format definition |
b2f/bcf_v0.1739529816.txt.gz · Last modified: 2025/02/14 10:43 by f4hof