F4HOF

User Tools

Site Tools

Trace:
b2f:bcf_v0

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision		Previous revision
b2f:bcf_v0 [2025/02/14 10:43] – [Commands] f4hofb2f: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 Modes =====+===== Transfer Mode =====
  
 The message/file payload is transferred using a different format from the ASCII Basic Protocol. The message/file payload is transferred using a different format from the ASCII Basic Protocol.
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 Mode ====+ 
 +As with the underlying protocol, the channel direction is immediately reversed after the completion of a transfer batch. 
 +==== ASCII Message Transfer Header ====
  
 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 Mode ====+==== Binary File Transfer Header ====
  
 FIXME proposal format definition FIXME proposal format definition
b2f/bcf_v0.1739529816.txt.gz · Last modified: 2025/02/14 10:43 by f4hof