> > This might be exactly what's needed if you're, say, teaching a programming > class where you want students to learn to use Subversion for version control > of their projects. You don't want students to be able to mess with each > others' code, and you probably don't want to retain their data forever once > the class is over. > I don't know if that's the original poster's situation, but that's what it > immediately reminded me of. >
Thanks for a great example. My situation is quite similar to what you describe actually, but consider _lots_ of students. This can be also compared to some projects hosting service with multiple projects hosted (and a repository for each), and multiple users accessing each project repository. I believe multiple separate repositories work much faster in this case than a single one, also there's absolutely no need for a single versions set - every student or project _must_ know nothing about others. The only problem as I wrote before is automatic authorization - the user A with the password B tries to access the repository C, and the information whether or not A is allowed to access C (and whether A's password is valid) is stored in MySQL due to the size of the users database and because of interoperability with other subsystems like external user management. I need to implement such authorization with as little coding as possible, optimally simply by using standard httpd/mod_dav_svn configuration options, so semi-standard extra modules and probably simple scripts.
