inheritable stuff (was: Roadmap for 1.1)

On Thu, Apr 01, 2004 at 10:03:15PM -0500, Mark Benedetto King wrote:
> On Thu, Apr 01, 2004 at 11:52:00PM +0200, Branko ??ibej wrote:
> >
> > The trouble with inheritable properties is that I can't think of an
> > efficient way to implement them without fiddling with the FS schema. Not
> > saying ideas wouldn't be welcome, of course. Personally, though, they're
> > not high on my list for 1.1.
> >
>
> Since paths are looked-up one segment at a time, couldn't we just
> keep a rolling inherited-properties context?

That is true in today's system, but not in all systems. I can easily see
using the full path as a key in a SQL-based system. In systems like this,
inherited properties and ACLs become a *real* bitch.

Also, if you "zoom in" to a specific node (say, via a copy reference),
then you are skipping the whole parent path processing. You'd have to then
try to figure out which path was used, break that down into segments, and
do the lookups.

It's for reasons like this why NTFS does not have inherited ACLs, but it
*does* default the values based on the parent. A "tear off copy", if you
will.

Cheers,
-g

-- 
Greg Stein, http://www.lyra.org/
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org