4 ms·
"Obviously, with sets, the location can be described in several ways, so it is not a Unique Resource Locatior - only RL." Wouldn't it be possible to implement
by Hexstream 17y ago
"Obviously, with sets, the location can be described in several ways, so it is not a Unique Resource Locatior - only RL."
Wouldn't it be possible to implement the filesystem with tags and then specify an ordering of the tags to map the graph into the usual hierarchy? The first part of the URI would specify the mapping (maybe just a name for a particular mapping), and the second would traverse the hierarchical view in the usual way.
This way, legacy apps could still think in terms of a tree while exposing a more powerful structure to new apps.
- dejan 17y agoYes it would, but then the need for it is dim. This was my biggest concern, to be backward compatible with legacy apps. And it is possible. "C:\Program Files\X\Y\Z" - "C"+"Program Files"+"X"+"Y"+"Z" "/usr/local/files/" - "usr"+"local"+"files" The only thing is that "usr" owns the file and so do "local" and "files" but the app doesn't care about that. Legacy apps do not access the files directly but through the filesystem. If the filesystem knows how to convert these conventional paths into sets, there is no problem.
- silentbicycle 17y agoI think worrying too much about reverse compatibility may be a bad idea. With access to relational features, the filesystems would probably be organized completely differently. Probably better to have a clean break.
- dejan 17y agoI agree, but it seems natural using the same paths. No patches to the concept would be needed.