Cart
[Home] [By Thread] [By Date] [Recent Entries]
> Eclipse provides a sort of virtual filesystem within its > workspace. The > workspace represents the filesystem root, with each project being an > immediate child folder of the workspace (regardless of where > they actually > lie in the filesystem). For example, a file called "bar" in > the project > "foo" would have the absolute path of "/foo/bar", even though > the actual > path in the filesystem might look something like > "c:\eclipse\projects\foo\bar" (just as a hypothetical > example). I'd like to > use URIs whose paths match the view presented to the user within the > workspace. > > What's the best way to do this? Would representing the above file as > "file:///foo/bar" be abusing the "file" URI scheme since it > doesn't match > the actual file path? The cleanest approach would be to make it not just a "sort of virtual filesystem", but a true virtual filesystem, and then your ethical dilemma disappears, and you also get lots of spin-offs like the ability to browse the virtual filestore using Windows Explorer and to upload files using FTP. If you don't want to do that, you could still decide that that's your target architecture, but in the short term you're only going to provide the URI access and not the rest: which means that using a file:// URI is the right thing to do because it matches the target architecture. Mike Kay
|
