[BOB] Re: [vfs] introduction

  • From: "Bas Westerbaan" <bas.westerbaan@xxxxxxxxx>
  • To: projectbob@xxxxxxxxxxxxx
  • Date: Thu, 1 Mar 2007 19:55:40 +0100

A few pratical examples:

* all objects (files/directories/..) will have tags. A .mp3 would have its
tags directly in the filesystem, no need to set the (slow to retreive and
set) tags in the mp3 format itself. Tags will be indexed within the
filesystem, so access to all your music will be uniform and fast form all
audio software.
* query's to the filesystem will have a POSIX path equivelent. When you'd
type "cd '[artist/Emperor]'" you'll be in a virtual directory with all files
with the Emperor tag.
* Icons, previews, filetypes can all be stored in tags on objects. This
means that listing directory contents in a graphical browser will be as fast
as an ls. Currently this isn't the case because of all the lookups.

Each object (file/directory/device ...) defines its own set of actions for
the system calls and types can be added on the fly. Objects will have full
inheritance. This allows for programs to define customs actions on certain
objects (files). You might be able to browse a .zip file bij 'cd'-ing to it
without extracting it or using a browser or have the program to be aware of
it.

This integration allows also for version control extensions natively in the
VFS. No need for (slow) '.svn' folders on your subversion repository.



--
Bas Westerbaan
GPG 99BA289B | SINP bas@xxxxxxxx
http://blog.w-nz.com/

Other related posts: