>To me it starts to sounds as though you have misunderstood the concept of the IMAP FS. The IMAP FS will not work by mapping files in the BFS file system elsewhere. It is completely in control of the exposed file system contents. For example, it >can publish an e-mail file and advertise a certain file size. This happens by way of implementing the file system hooks and just declaring objects to be there. They don't have to exist on the harddrive at all. Advertising a certain file size does not >mean the e-mail is already downloaded in full Hmm.I got the point. Can we discuss more in terms of implementation? As i understand it, IMAP FS will make vnodes and create the file metadata from the data fetched initially, i.e. headers. Now, when the fs_vnode_ops::read<http://api.haiku-os.org/structfs__vnode__ops.html#a3d5f1013644389c3efee43b3e175aa34>hook is called, instead of getting data from the disk, it gets it from the user's IMAP account, also optionally saving it(in another Filesystem). The read hook is an example, similar things would be done with other hooks. Am i reading this right? Also, it would be great if you can point to some FS that does this i.e. gets data from a source other than disk. Is NetFS relevent?