--- Branko Čibej <brane@xbc.nu> wrote:
> This particular can of worms can only closed by way
> of a change in the
> repository schema. The inheritance must be made
> explicit, while at the
> same time not requiring an O(n) tree traversal every
> time an inherited
> property is changed. In other words, an object's
> proplist must contain
> links to the inherited values.
>
> The problem -- and its solution -- is really quite
> similar to ACL
> inheritance, except that properties are versioned
> and ACLs aren't.
I believe Win2k ACL inheritance is done this way. The
problem they face is when items move.
For example, if an item inherits a property from its
parent directory, then it moves, do the inherited
values travel with it? Or does it now inherit from
the new directory?
Both choices have their pro's and con's. If inherited
properties were done in this fashion, it may be better
to leave the choice of mv-behaviour to the user/admin.
> Dare I utter that most despised phrase, "post-1.0?"
There have been too many lingering issues brought up
with this. Unless the simpler version of "copied
properties" were done, I agree with you that inherited
properties should be post-1.0.
MTC,
Noel
__________________________________________________
Do you Yahoo!?
HotJobs - Search new jobs daily now
http://hotjobs.yahoo.com/
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Mon Nov 4 13:54:29 2002