[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

RE: How much libsvn_repos wrap around the libsvn_fs

From: Nitin Shukla <nitinshukla_at_infotech.stph.net>
Date: 2002-12-24 09:50:13 CET

Has there been any approach to develop the read hook scripts?
I know that the read sentinels are yet to be implemented and
is supposed to communicate with the Subversion server using
protocol which not decided yet. Probably LDAP can be used
if we can make Subversion server understand LDAP protocols.
If anyone has thought any approach i.e. developing read hook
scripts and/or implementing the read sentinels pls. update me.
Is there any such work going on in the Subversion Development
community?

"Nitin Shukla" <nitinshukla@infotech.stph.net> writes:

> I am interested in knowing what are the other events which will be
> interfaced by the repository access library, as these would empower hooks
to
> have fine control over the access to the repository?

Someday we hope to have not just 'write' hooks (start-commit,
pre-commit, post-commit), but 'read' hooks as well: these would
somehow create pipes to long-running hook processes (we call them
"sentinels") that would allow or disallow clients to read specific
paths in the repository.

Nitin, maybe we should cut to the chase here. :-) I know that you've
been assigned to implement some kind of fine-grained ACL system on top
of Subversion. There are three ways you can do this, I believe, in
increasing order of complexity:

1. Write an custom apache module to do authentication of every
    incoming HTTP request to the Subversion repository. Your apache
    module could speak to a database containing ACLs. It's easy for
    your module to distinguish between read requests (GET, PROPFIND,
    OPTIONS, REPORT) and write requests (PUT, PROPPATCH, COPY, etc.)

2. Write some complex write-hook programs, using the existing hook
    feature in libsvn_repos. Presumably these write-hook programs
    would also speak to a database containing ACL information. That's
    the easy part: the harder part is the fact that we don't yet have
    any read-hooks. We'd need to design that feature and add it to
    libsvn_repos.

3. Design an ACL system that is inherent to libsvn_fs. This is the
    difficult theoretical problem that nobody has been able to tackle
    yet. It's very hard.

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Tue Dec 24 09:51:25 2002

This is an archived mail posted to the Subversion Dev mailing list.