This is the mail archive of the cygwin-apps@cygwin.com mailing list for the Cygwin project.
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |
Other format: | [Raw text] |
Hello Robert, Tuesday, May 07, 2002, 12:45:33 PM, you wrote: RC> I'd like to formalise what file:// and cygfile:// schemes mean. RC> file:// is a native filesystem URL handler - whatever the OS may be. RC> cygfile:// is a handler that only makes sense on mingw platforms, and RC> access's the cygwin mount table. There is no cygfile://. There is no authority in the cygfile schema - only path. // leads to authority. I think of cygfile as a UNIX/posix path. RC> This means that: RC> file:///foo/bar.txt is /foo/bar.txt on posix, and Current RC> drive:\foo\bar.txt on mingw. No. file:///foo/bar.txt is not parsed. RC> As for file:// + d: + \foo\bar.txt, can we normalise that as RC> file://d|/foo/bar.txt - that is what MS do, and will be less confusing RC> for users of the codebase (IMO). How would this confuse them ? I don't think with file://d|/foo/bar.txt is better thatn file://d/foo/bar.txt. There is a method which converts d:\foo\bar to file URL - isn't it enough ? There is also a method whic gets the parsed URL as path. Btw see the attached program. It is a test for the URL parser.
Attachment:
URLTest.zip
Description: Zip compressed data
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |