Posted by: Anonymous Coward
on October 24, 2003 11:00 PM
This approach allows for virtual folders, which could have files from the user's computer, from the Internet, or from other computers across the globe. To make access faster, containers would be automatically indexed in real time.
And then what happens if the network connection fails (ISP gateway slows to a crawl, etc) while using this nicely indexed virtual filesystem? Wait for each time the system tries to connect to a file to time out then delete it from the index. Your computer would probably freeze. Ever have a system with an autofs mounted nfs directory mounted and have the nfs server die? The results are not pretty. If every item is an object with properties other than just file attributes, and those properties have to be read or held in memory how to do you compensate for all the extra cpu cycles and memory to deal with these objects? Sometings look realy great on paper but when you actually sit down and try to implement them, reality sets in and you end up going with what works best.
Learn about Linux
Download Linux
Get Linux help
Object Filesystem
Posted by: Anonymous Coward on October 24, 2003 11:00 PMAnd then what happens if the network connection fails (ISP gateway slows to a crawl, etc) while using this nicely indexed virtual filesystem? Wait for each time the system tries to connect to a file to time out then delete it from the index. Your computer would probably freeze. Ever have a system with an autofs mounted nfs directory mounted and have the nfs server die? The results are not pretty. If every item is an object with properties other than just file attributes, and those properties have to be read or held in memory how to do you compensate for all the extra cpu cycles and memory to deal with these objects? Sometings look realy great on paper but when you actually sit down and try to implement them, reality sets in and you end up going with what works best.
#