> Yes, the problem seems to be that mod_authz_svn has no way of storing per-connection state at present.
Please excuse the interjection here: My eyes spied "per connection" and I wondered if something I'm doing elsewhere that is closer (but not exactly) "per user" might help in terms of thinking. I've a server-side 'wrapper' around Svn that's calculating authz permutations for each *user*. That transcends any sessions and connections for the user. Two users in the same groups(s) with no other variance in authz config will use the same cached Svn entries everywhere. I've speedy unit tests too for it, but I've a ways to go because of the exclude grammar of authz's little language. If the thing works well enough, but eats too much of the disk-backed-ram-cache <http://www.mapdb.org/> I'm using, I could extend it to do the same per directory. Because right now it is effectively a 'from root of repo' determination for a user. Of course, you don't want the code I've done because it is not compatible with the current Svn toolchain. I'm thinking about a Rust rewrite, but that's a year away, even if it was compatible with the way Subversion is today. Regards, - Paul
