Re: Milestone 2: authentication and authorization

> > It's very important to realize that node revision numbers are *not*
> > inode numbers.
>
> Ouch. Of course.
>
> O.K., that leaves two alternatives:
>
> a) Treat an ACL change as a modification, and create a new revision at
> that time. This probably won't work, though, because ACL changes would
> become expensive.
>
> b) Put the ACLs in the directory entries, beside the entry names. This
> would bring us close to how an actual filesystem behaves.
>
> I'd go for b). Opinions?

Doesn't help, I think. Directories get shared, too.

I'm thinking of some table indexed by path, then revision number, with
some nice, meaningful ordering to allow range searches...
Received on Sat Oct 21 14:36:17 2006