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:44] – [Transfer Modes] f4hof | b2f:bcf_v0 [2025/02/14 10:45] (current) – [Binary File Transfer Mode] f4hof | ||
|---|---|---|---|
| Line 33: | Line 33: | ||
| As with the underlying protocol, the channel direction is immediately reversed after the completion of a transfer batch. | As with the underlying protocol, the channel direction is immediately reversed after the completion of a transfer batch. | ||
| - | ==== ASCII Message Transfer | + | ==== ASCII Message Transfer |
| FIXME proposal format definition | FIXME proposal format definition | ||
| Line 54: | 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.1739529897.txt.gz · Last modified: 2025/02/14 10:44 by f4hof