TVFS
Click on the red underlined text to get to the source
...
Except where TVFS is supported (see section 6), this specification
imposes no syntax upon pathnames. Nor does it restrict the character
set from which pathnames are created ...
... A Trivial Virtual File Store (TVFS) ...
... FTP provides no guaranteed
mechanism to return to a previous directory. The Trivial Virtual
File Store (TVFS), if implemented, provides that mechanism.
...
... TVFS File Names ...
...
Where a server implements the TVFS, no elementary file name shall
contain the character "/". Where the underlying natural file store
permits files, or directories, to contain the "/" character in their
...
... 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
the user-PI ...
...
With the one exception of the unnamed root directory, a TVFS file
name may not be empty. That is, all other file names contain at
least one character.
...
... valid IS10646
character [10] may be used in a TVFS file name. When transmitted,
file name characters are encoded using the UTF-8 encoding [2 ...
... TVFS Pathnames ...
...
A TVFS "Pathname" combines the file or directory name of a target
file or directory, with the directory names of zero or more enclosing
...
... target file or directory.
By definition, every TVFS file or directory name is also a TVFS
pathname. Such a pathname is valid ...
...
By definition, every TVFS file or directory name is also a TVFS
pathname. Such a pathname is valid to reference the file from the
...
... current working directory.
Other TVFS pathnames are constructed by prefixing a pathname by a
name of a directory from which the path is valid, and separating the
...
... directory.
+ As a caveat, though the TVFS file store is basically tree
structured, there is no requirement ...
... have only one parent directory.
+ As defined, no TVFS pathname will ever contain two consecutive "/"
characters. Such a name is not illegal however, and may be
defined by the server ...
... + Similarly, other than the special case path that refers to the
root directory, no TVFS pathname constructed as defined here will
ever end with the "/" character. Such names are also not illegal,
but are undefined.
...
... but are undefined.
+ While any legal IS10646 character is permitted to occur in a TVFS
file or directory name, other than "/", server FTP implementations
...
... but are not required to do so.
+ TVFS imposes no particular semantics or properties upon files,
guarantees no access control ...
... FEAT command [6] a server that wishes to indicate
support for the TVFS as defined here will include a line that begins
with the four characters "TVFS" (in any case, or mixture of cases,
...
... support for the TVFS as defined here will include a line that begins
with the four characters "TVFS" (in any case, or mixture of cases,
upper case is not required). Servers SHOULD send upper case.
...
... Such a response to the FEAT command MUST NOT be returned unless the
server implements TVFS as defined here.
Later specifications may add to the TVFS ...
... TVFS as defined here.
Later specifications may add to the TVFS definition. Such additions
should be notified by means of additional text appended to the TVFS
...
... Later specifications may add to the TVFS definition. Such additions
should be notified by means of additional text appended to the TVFS
feature line. Such specifications, if any, will define the extra
text.
...
...
Until such a specification is defined, servers should not include
anything after "TVFS" in the TVFS feature line. Clients, however,
...
... Until such a specification is defined, servers should not include
anything after "TVFS" in the TVFS feature line. Clients, however,
should be prepared to deal with arbitrary text following the four
...
... S> 211- <any descriptive text>
S> ...
S> TVFS
S> ...
S> 211 end
...
... four characters for the purposes of this feature listing.
The TVFS feature adds no new commands to the FTP command repertoire.
...
... OPTS for TVFS ...
...
There are no options in this TVFS specification, and hence there is
no OPTS command defined.
...
... TVFS Examples ...
...
Assume a TVFS file store is comprised of a root directory, which
contains two directories (A and B) and two non-directory files (X and
...
... fully qualified path with "/A/" prepended.
That those pathnames all exist does not imply that the TVFS sever
will necessarily grant any kind of access rights to the named paths,
...
... "P" and "Q" might refer to different files depending upon which
directory is selected to cause those to become valid TVFS relative
paths.
...
... entity in the server NVFS which is not a directory. Where TVFS is
supported, any TVFS relative pathname valid ...
... NVFS which is not a directory. Where TVFS is
supported, any TVFS relative pathname valid in the current working
directory, or any TVFS ...
... TVFS relative pathname valid in the current working
directory, or any TVFS fully qualified pathname, may be given. If a
directory name is given then MLSD must return a listing of the
...
... MLST response should be the same name
as was specified in the MLST command, or, where TVFS is supported, a
fully qualified TVFS path naming the same file. Where no argument
...
... MLST command, or, where TVFS is supported, a
fully qualified TVFS path naming the same file. Where no argument
was given to the MLST command, the server-PI ...
... 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 is
supported, a fully qualified pathname of the current directory SHOULD
be returned.
...
... MLSD response, an entry whose type is
"cdir", which names the directory from which the contents of the
listing were obtained. Where TVFS is supported, the name MAY be the
fully qualified pathname of the directory, or MAY be any other
pathname that is valid ...
... occur anywhere within the listing.
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 of the directory from an entry in the directory.
Where TVFS is supported by the server-FTP, this name may be used to
...
... issued, unless a fully qualified pathname results.
Where TVFS is not supported, the only defined semantics associated
with a "type=cdir" entry are that, provided the current working
directory ...
... multiple type=pdir responses.
Where TVFS is supported, a "type=pdir" name may be a relative
pathname, or a fully qualified pathname. A relative pathname will be
relative to the directory being listed, not to the current directory
...