On Thu, Jul 29, 2004 at 06:29:08PM +0200, Frank Strau? wrote:
When the repository is accessed through system calls on the filesystem and their access control mechanism (user, group, file mode), it is not possible to control who is allowed to access which projects within a repository. (In CVS it was due to the CVSROOT/ stuff, in SVN all data sits in a single Berkeley DB.) The only alternative would be to create separate repositories per project and one UNIX group per repository and hoping not to exceed the OS' limit of groups per user. Furthermore, I'd like to safely exclude the eventuality that the repository is accessed via NFS, which could cause strange problems due to incompatible locking mechanisms.
I do not care about direct access to the files. But I do not understand the difference between talking SVN native to the svnserv daemon and talking webdav when it comes to access control. In both cases, I think access control is implement in one of the server processes.
Anyway, if you prefer to go with webdav, feel free to do. I will be able to adapt to it.
/js