How to protect checkout of code for multiple modules within a project using SVN

We have several independent modules (e.g. mod1, mod2, mod3 ...) under a project 'proj1'. How to protect checkout of code for multiple开发者_如何学C modules within a project using SVN.

We would like to provide user1 access to proj1/mod1 and user2 to proj1/mod2 and .... Would this be possible or should I have to create multiple projects.

Subversion was designed so that different people could work on the same projects. Team updates coordinate the changes across multiple work environments.

In Subversion, you have to check out at a folder level. You cannot check out an individual source module. You would have to put mod1, mod2, mod3, etc. in separate folders.