Re: Vnode scope implementation

[der Mouse <mouse%Rodents-Montreal.ORG@localhost>]

> Some things that will not (cannot!) change:

>   - there will be some concept of a locked vs. an unlocked vnode;
>   - to avoid race conditions, any vnode on which access control
>     checks are being made must be locked, and stay locked, from
>     before the check is made to after the operation is complete;

I don't expect these will change.  But I think it is probably excessive
to say they cannot change, except in a pragmatic/practical sense.  I've
seen some very clever algorithms for access to shared data structures
without the need for anything like locking, and, while it's not obvious
to me how they could be applied to anything like vnodes, I am by no
means convinced they can't be.

/~\ The ASCII                             Mouse
\ / Ribbon Campaign
 X  Against HTML                mouse%rodents-montreal.org@localhost
/ \ Email!           7D C8 61 52 5D E7 2D 39  4E F1 31 3E E8 B3 27 4B