Re: svn commit: r1614080 - in /subversion/branches/authzperf: BRANCH-README subversion/libsvn_repos/authz.c subversion/libsvn_subr/config.c subversion/libsvn_subr/config_impl.h

Brane wrote:
> if the patterns were:
>
>    [*/projects/f*/include/*.h]
>    [*/projects/*o/include/*.h]

(Ugh, I don't like the prefix '*' which I think you're using to mean 'wildcards enabled'.)

> where both "f*" and "*o" match "foo", we should always pick
> whichever pattern was defined first in the authz file.

So if the (wildcard-enabled) patterns were

    /projects/*/include/*.h
    /projects/foo_*/include/foo.h

then for a path that matches both we'd always pick the pattern defined first, because in the first (most significant) path component where the patterns differ, neither provides an exact match. In this case we'd pick the one that intuitively looks a 'looser' match.

1. Do these rules match any other existing practice that we could compare with?

2. Are these rules documented in the authzperf branch yet?

3. Do these rules match the behaviour Stefan is currently implementing in the authzperf branch?

Just wondering.

- Julian
Received on 2014-07-29 12:26:21 CEST