"Tony Lewis" <[EMAIL PROTECTED]> writes: > Hrvoje Niksic wrote: > >> Wget could always support a URL parameter, such as: >> >> wget 'ftp://server/dir1/dir2/file;disk=foo' >> > > Assuming, you can detect a VMS connection, why not simply > ftp://server/foo:[dir1.dir2]?
Because it doesn't look like a URL. URL syntax already defines "directories" (path components) that can be translated into whatever syntax the FTP server understands. This uniformity is useful because it allows Wget, and other tools, to perform operations on URLs that would otherwise be impossible. For example, you can merge the base "ftp://server/dir1/dir2/"; with URI "../foo" to get something "ftp://server/dir1/foo";. If the URI syntax depended on the operating system on the remote FTP server, the URIs as we know them would not exist. (Also cf. the other thread where we are asked to implement the DOS backslash separator!)
