[openbeos] (Network) File Systems
- From: Mat Hounsell <mat_geek@xxxxxxxxxxxx>
- To: glasselevator@xxxxxxxxxxxx, openbeos@xxxxxxxxxxxxx
- Date: Tue, 6 Aug 2002 20:08:29 +1000 (EST)
On the OpenBeOS list someone (sorry) suggested allowing URL's as a mount
command. Meanwhile I have considered creating a http, ftp, odbc and clipboard
file systems.
To begin with a file system has complete control on the namespace it represents
and you can mount it at abritrary points in the file system. So "$> cat
/http://www.openbeos.org > ~/www.openbeos.org.html" would access the (read
only) http: file system which would then parse the domain name and then attempt
a http get.
While "$> cat /http://baron:password@localhost/etc/passwd > ~/security-risk"
would cause the http: file system to attempt a login and then a get.
This can be extended to any protocol.
The clipboard file system is trickier. The clipboard is (currently) an
application pull service that uses BMessages. Meaning the file system would
have to have a BClipboard object and decoded BMessages, ick.
Because these two examples bring up a single issue. If a file system is in the
kernel an kernel space how do you add incredible features without burdening the
kernel and risking it's stability?
http://digital.yahoo.com.au - Yahoo! Digital How To
- Get the best out of your PC!
Other related posts:
