Connected: An Internet Encyclopedia
RFC 959 - 3.1.1.4. LOCAL 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.3. IMAGE TYPE
Next: 3.1.1.5. FORMAT CONTROL

### 3.1.1.4. LOCAL TYPE

The data is transferred in logical bytes of the size specified by the obligatory second parameter, Byte size. The value of Byte size must be a decimal integer; there is no default value. The logical byte size is not necessarily the same as the transfer byte size. If there is a difference in byte sizes, then the logical bytes should be packed contiguously, disregarding transfer byte boundaries and with any necessary padding at the end.

When the data reaches the receiving host, it will be transformed in a manner dependent on the logical byte size and the particular host. This transformation must be invertible (i.e., an identical file can be retrieved if the same parameters are used) and should be well publicized by the FTP implementors.

For example, a user sending 36-bit floating-point numbers to a host with a 32-bit word could send that data as Local byte with a logical byte size of 36. The receiving host would then be expected to store the logical bytes so that they could be easily manipulated; in this example putting the 36-bit logical bytes into 64-bit double words should suffice.

In another example, a pair of hosts with a 36-bit word size may send data to one another in words by using TYPE L 36. The data would be sent in the 8-bit transmission bytes packed so that 9 transmission bytes carried two host words.

Next: 3.1.1.5. FORMAT CONTROL

Connected: An Internet Encyclopedia
RFC 959 - 3.1.1.4. LOCAL TYPE