[9fans] FS dimension

[northern snowfall <dbailey27@ameritech.net>]

> Just random thought, has anyone played with the concept of a stackable
> bind? i.e. instead of /net.alt bound over /net so that accessing /net/cs
> always thunks /net.alt/cs, make it so thunk one in the target dir
> accesses
> the top of the LIFO (/net.alt/cs), then, the successive thunk would
> access
> the lower object: the true /net/cs. This would generate a
> multidimensional
> file system rather than solely a linear. There could be fs calls for
> resetting the
> LIFO, somehow.. Just a thought.

Despite the effort it would take to put this theory into function, what
does everyone
think of the basic concept?
Instead of a filesystem accessed as:

    transparent access points
     -----v
        file1    file2    file3    ...
/path    obj1    obj2    obj3    ...  // actual internal FS objects

You now have stacked objective binds:
    % bind -stack ...
    transparent access points
     -----v
        file1    file2    file3    ...
/path2    obj1.2    obj2.2    obj3.2    ...    // second stacked bind
/path1    obj1.1    obj2.1    obj3.1    ...    // first stacked bind
/path    obj1    obj2    obj3    ...    // original

So a given access mechanism (AM) would open "/path/file1". This initial
thunk would pop "obj1.2" off "file1"'s LIFO to the AM. If this isn't the
desired object the AM can request a secondary open on the same path
"/path/file1", popping "obj1.1" off the LIFO, this time. This might be
interesting in database regression environments or, perhaps, stackable
networks. This was just off the top of my head, yesterday, but, I'd
like to know what this mailing group has to say regarding the idea.
Don



>