Re: SoC: Path-based authz for Svnserve

David Anderson wrote:

> ====A summary of questions for the busy people====
>
> - Is having a function in libsvn_repos that doesn't actually use a
> svn_repos_t acceptable, or should the authz routines move to another lib?

I don't see any especially pressing reason to move it to another lib.

> - How do we cache the authz file (svn_config_t) in svnserve? Keep it
> loaded and reload on SIGUSR1 or similar?

I'd rather you just stat the file to see if it's been modified or
something like that, requiring the user to send a signal to the process
seems rather error prone.

> - What enhancements to the authz file format are badly needed by the
> community?

Some way to indicate that a part of the tree can be accessed by a user
that is not logged in. I don't think mod_authz_svn can do that, but
svnserve might want to.

> - Is caching authz info in svnserve a stupid idea (see detailed
> proposal) ?

I'd say go without it for the first pass, just reading it in at the
start of a session, then after you've got it working look at how much of
a speed improvement there is when caching is added.

> - (for those who've had the courage to walk the rest of the proposal)
> Are there points to which ou object or on which you have further
> notes/comments/observations/flames ?

Seems reasonable to me, although I did only give it a quick read-through.

-garrett

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Wed Jun 29 18:53:02 2005