Connected: An Internet Encyclopedia
RFC 959 - 3.1.1.3. IMAGE TYPE

Top: Connected: An Internet Encyclopedia
Up: Requests For Comments
Up: RFC 959
Up: 3. DATA TRANSFER FUNCTIONS
Up: 3.1. DATA REPRESENTATION AND STORAGE
Up: 3.1.1. DATA TYPES
Prev: 3.1.1.2. EBCDIC TYPE
Next: 3.1.1.4. LOCAL TYPE

### 3.1.1.3. IMAGE TYPE

The data are sent as contiguous bits which, for transfer, are packed into the 8-bit transfer bytes. The receiving site must store the data as contiguous bits. The structure of the storage system might necessitate the padding of the file (or of each record, for a record-structured file) to some convenient boundary (byte, word or block). This padding, which must be all zeros, may occur only at the end of the file (or at the end of each record) and there must be a way of identifying the padding bits so that they may be stripped off if the file is retrieved. The padding transformation should be well publicized to enable a user to process a file at the storage site.

Image type is intended for the efficient storage and retrieval of files and for the transfer of binary data. It is recommended that this type be accepted by all FTP implementations.

Next: 3.1.1.4. LOCAL TYPE

Connected: An Internet Encyclopedia
RFC 959 - 3.1.1.3. IMAGE TYPE