text stringlengths 0 99.6k |
|---|
Parameters are received than the entity understands, then |
any beyond the last received parameter must be treated as if |
it was provided as 0x00, which must be its default value. |
See Section "E. Negotiation of Transport Parameters" for |
details on deciding what level of capabilities each entity |
is to use. |
9 |
b) Packet Type `T': File Transfer. |
The File Transfer Packet consists of three fields as |
follows: |
<Direction> <Data type> <File name> |
1) Function. |
`D' = Download (Initiator -> Responder) |
`U' = Upload (Responder -> Initiator) |
`C' = Close. End of Upload or Download |
(Note: Additional "T" packets are defined later.) |
2) Data type. |
`A' = 7-bit ASCII data. (Allows for End of Line |
conversion.) |
`B' = 8-bit Binary data. |
`I' = Image data. (This is hardware specific data and |
usually consists of some embedded header which |
describes the remainder of the file. It is |
always 8-bit binary data.) |
3) File Name. |
This field is variable length and specifies the name of the |
file to be transfered. |
A sample File Transfer packet using CRC Check Method is: |
<DLE> B 7 T D A S . C <ETX> 0x57 0xff |
0x10 0x42 0x37 0x54 0x44 0x41 0x53 0x2e 0x43 0x03 0x57 0xff |
which specifies: |
o `T': File Transfer |
o `D': Download to the Responder |
o `A': This is an ASCII file |
o `S.C': The file name |
Note that there are no guidelines as to what the Responder |
is to do with the File Transfer packet. In particular, the |
implementor is free to locally verify the request, permit |
the file name to be changed, etc. |
If the Responder does not wish to comply with the request |
made in the File Transfer packet, a Failure Packet must be |
returned to the Initiator. |
10 |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.