> Ah, another person getting burned by the outdated design doc ;)
> Can we please update the doc? Or at least remove the auth/authz
> section and place a TBD in there?
That would be nice. TBD would suffice:-)
> There were several quite long threads about this on the mailinglist.
> Please search the archives and seek them out. ACLs are not scheduled
> for 1.0 IIRC. We do have consensus with respect to needing ACLs at some
> point though.
I'll dig into this when I get back to this issue.
> > I actually started to develop an Apache 2.0 module to handle all of this
> > outside of subversion. I have stopped for the time being as It seemed
> > like I was heading in the wrong direction. I need it for something else
> > I'm doing, so I will complete it at some point.
> There are some issues with respect to doing fine grained access control
> with Apache. Greg Stein and I tried to come up with an Apache configuration
> that did fine grained access control, but we got bitten by the so
> called '$svn' url.
Not sure what you mean here, but what halted me was the idea that a given URL
"name" can point to different nodes over time. wooaa. I planned on the ACLs
being contained outside subversion at first. No No No. Once I thought about it,
I freaked and stopped. It has to be in the Repos to work.
> > Please Please clarify this whole thing for me folks.
> The current status is that ACLs are put on hold for now. But ofcourse
> anyone with enough time could provide patches ;)
I guess what I'm asking is: do you guys have a design of some sort for ACLs. Or
even a loose set of requirements.
As for patches:-)
I'm currently working on building a SQL FS. Yes, I really am.
Patches are a ways off. I'm spinning up a little slower than I had hoped but
I'm making progress.
I changed my approach when cmpilato started working on the skel separation and I
learned of the unbounded key issue.
That reminds me, I need to update. It's been hours. Mike could had checked in
several hundred files by now:-)
So while all that is fleshing out, I'm playing with how to ask the basic
ancestry/hierarchy questions of a SQL store and what that SQL store should look
like. Once I can defend my approach "OH and I have one:-)", I will post ERDs
and perhaps a few SQL scripts to demonstrate the basic query accesses I will
need. I will most likely have more tables than the BDB FS has.
woooaaa sorry to switch subjects on you.
Thanks for the response,
To unsubscribe, e-mail: email@example.com
For additional commands, e-mail: firstname.lastname@example.org
Received on Thu May 23 10:29:47 2002