server-PI
Click on the red underlined text to get to the source
...
Which format is used is at the option of the user-PI or server-PI
sending the pathname. UTF-8 encodings ...
... 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,
it is far more important for the user-PI to be able to retain and
...
... manner appropriate to their implementation or underlying file system.
Similarly, a server-PI may parse the pathname and assign meaning to
the components detected.
...
... calendar regardless of what calendar may have been in use at the date
and time indicated at the location of the server-PI.
The technical differences among GMT ...
... digit code that is their first element. Thus the term "500 reply"
means a reply from the server-PI using the three digit code "500".
...
... control connection from the user-PI to
the server-PI, lines that begin "S> " were sent over the control
connection from the server-PI to the user-PI ...
... the 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 ...
... server-PI to the user-PI, and each sequence of
lines that begin "D> " was sent from the server-PI to the user-PI
over a data connection ...
... PI.
The server-PI will respond to the MDTM command with a 213 reply
giving the last modification time ...
... MDTM command may behave as indicated. The
"C>" lines are commands from user-PI to server-PI, the "S>" lines are
server-PI replies.
...
... STREAM mode, to determine the restart point. The server-PI might
need to read the partially transferred file, do any appropriate
conversion, and count the number of octets that would be generated
...
... CRLF
The server-PI will respond to the SIZE command with a 213 reply
giving the transfer size of the file whose pathname was supplied, or
an error response ...
...
Since calculating the size of a file with this degree of precision
may take considerable effort on the part of the server-PI, user-PIs
should not used this command unless this precision is essential (such
...
... effectively disables restart, causing the entire file to be
transmitted. The server-PI will respond to the REST command with a
350 reply, indicating that the REST ...
... file transfer. The effect of issuing a REST command at any
other time is undefined. The server-PI may react to a badly
positioned REST command by issuing an error response ...
... contain the character "/". Where the underlying natural file store
permits files, or directories, to contain the "/" character in their
names, a server-PI implementing TVFS must encode that character in
some manner whenever file or directory names are being returned to
...
... itself. For these purposes, the contents of a directory are whatever
file or directory names (not pathnames) the server-PI will allow to
be referenced when the current working directory is the directory
...
... be referenced when the 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
...
... the directory happens to be known. In particular, there is no
defined shorthand name for the current directory. This does not
prohibit any particular server-PI implementing such a shorthand.
No title, header ...
... If the parameter is valid, then for an MLST command, the server-PI
will send the first (leading) line of the control response, the entry
for the pathname given, or the current directory if no pathname was
...
... TVFS path naming the same file. Where no argument
was given to the MLST command, the server-PI may either include an
empty file name in the response, or it may supply a name that refers
to the current directory, if such a name is available. Where TVFS ...
... returned in the same MLSD output (see section 6.2). These pathnames
are only expected to work when the server-PI's position in the NVFS
file tree ...
... semantics associated
with a "type=cdir" entry are that, provided the current working
directory of the server-PI has not been changed, a pathname of type
"cdir" may be used as an argument to a CWD command, which will cause
...
... "cdir" may be used as an argument to a CWD command, which will cause
the current directory of the server-PI to change so that the
directory that was listed in its current working directory.
...
... pathname, or a fully qualified pathname. A relative pathname will be
relative to the directory being listed, not to the current directory
of the server-PI at the time.
For the purposes of this type value ...
... the appropriate type, and each containing the same pathname. This
may occur, for example, with a structured file, which may contain
sub-files, and where the server-PI permits the structured file to be
treated as a unit, or treated as a directory allowing the sub-files
...
...
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
...