Connected: An Internet Encyclopedia
RFC 1123 - 4.1.2.4 Data Structure Transformations: RFC-959 Section 3.1.2

Top: Connected: An Internet Encyclopedia
Up: Requests For Comments
Up: RFC 1123
Up: 4. FILE TRANSFER
Up: 4.1 FILE TRANSFER PROTOCOL -- FTP
Up: 4.1.1 INTRODUCTION
Prev: 4.1.2.3 Page Structure: RFC-959 Section 3.1.2.3 and Appendix I
Next: 4.1.2.5 Data Connection Management: RFC-959 Section 3.3

### 4.1.2.4 Data Structure Transformations: RFC-959 Section 3.1.2

An FTP transformation between record-structure and file- structure SHOULD be invertible, to the extent possible while making the result useful on the target host.

DISCUSSION:

  RFC-959 required strict invertibility between record- structure and file-structure, but in practice, efficiency and convenience often preclude it. Therefore, the requirement is being relaxed. There are two different objectives for transferring a file: processing it on the target host, or just storage. For storage, strict invertibility is important. For processing, the file created on the target host needs to be in the format expected by application programs on that host.

  As an example of the conflict, imagine a record- oriented operating system that requires some data files to have exactly 80 bytes in each record. While STORing a file on such a host, an FTP Server must be able to pad each line or record to 80 bytes; a later retrieval of such a file cannot be strictly invertible.

Next: 4.1.2.5 Data Connection Management: RFC-959 Section 3.3

Connected: An Internet Encyclopedia
RFC 1123 - 4.1.2.4 Data Structure Transformations: RFC-959 Section 3.1.2