RFC 3659:Extensions to FTP
RFC-Ref

user-PI


Click on the red underlined text to get to the source

... DTP" (data transfer process), "user-FTP process", "user-PI" (user protocol interpreter), "user-DTP", "server-FTP process ...
... UTF-8 encoding> Which format is used is at the option of the user-PI or server-PI sending the pathname. UTF-8 ...
... UTF-8 or raw encoding has been used, in those cases where it matters. While it is useful for the user-PI to be able to correctly display a pathname received from the server-PI to the user, ...
... correctly display a pathname received from the server-PI to the user, it is far more important for the user-PI to be able to retain and retransmit the identical pathname when required. Implementations are advised against converting a UTF-8 ...
... by the server-PI to FTP commands from the user-PI. Those reply conventions are used here without change. ...
... FTP dialogs presented in this document, lines that begin "C> " were sent over the control connection from the user-PI to the server-PI, lines that begin "S> " were sent over the control connection ...
... server-PI, lines that begin "S> " were sent over the control connection from the server-PI to the user-PI, and each sequence of lines that begin "D> " was sent from the server-PI to the user-PI ...
... user-PI, and each sequence of lines that begin "D> " was sent from the server-PI to the user-PI over a data connection created ...


... files at all, then the MDTM command may behave as indicated. The "C>" lines are commands from user-PI to server-PI, the "S>" lines are server-PI ...


... command, or it may silently ignore the inappropriate restart attempt. Because of this, a user-PI that has issued a REST command, but that has not successfully transmitted the following data transfer ...


... TVFS must encode that character in some manner whenever file or directory names are being returned to the user-PI, and reverse that encoding whenever such names are being accepted from the user-PI ...
... user-PI, and reverse that encoding whenever such names are being accepted from the user-PI. The encoding ...


... current working directory is the directory named, and which the server-PI desires to reveal to the user-PI. Note that omitting the argument is the only defined way to obtain a listing of the current directory, unless a pathname that represents ...
... When TVFS is supported, a user-PI can refer to any file or directory in the listing by combining a type "cdir" name, with the appropriate name from the directory listing using the procedure defined in ...
... Alternatively, whether TVFS is supported or not, the user-PI can issue a CWD command ([3 ...
... start, though frequently may do so, and may occur multiple times. It MUST NOT be included if the type fact is not included, or there would be no way for the user-PI to distinguish the name of the directory from an entry in the directory. ...
... lifetime of the control connection from user-PI to server-PI. ...
... By using an system dependent fact, or a local fact, a server-PI may communicate to the user-PI information about the file named that is peculiar to the underlying file system. ...


... MLST" commands before authentication of the user-PI, but may choose to permit them. ...



Google
Web
RFC-Ref