Josef RIESENEDER <riesene...@racon-linz.at> writes: > I have an suggestion for checking the user access. It would be nice to use > a regex in the path instead of the full path. > > Instead of this: > [/currTree/trunk/config] > @user = rw > [/currTree/branches/branch1/config] > @user = rw > > It should be possible to use simply a regex: > [/currTree/.*/config] > @user = rw
What happens with multiple matches? Can you define a consistent set of rules that will allow people to predict the behaviour? Given: [/foo/.*/bar] @user = rw [/foo/.*] @user = [/.*/bar] @user = r [/f.*/z.*/b.*] @user = r [/foo/zig/bar.*] @user = rw What access does @user have to /foo/zig/bar? One possibility is that we get the union of all the matches; this has similarities to [/foo/zig/bar] @users = r @admin = rw where a name that is present in @users and @admin gets r+rw=rw. -- uberSVN: Apache Subversion Made Easy http://www.uberSVN.com
