Karl Heinz Marbaise wrote on Thu, Dec 27, 2012 at 16:03:55 +0100: > Network: working-copy-1 > User 1 accesses working-copy-1 and changes some files and will checkin > those changes. > > User 2 accesses working-copy-1 and changes some files and will checkin > those changes. > etc. > > My knowledge is that if those accesses to the above working copy can be > handled strictly sequential it might work but i'm not 100% sure..(may be > someone can give more detailed informations).. >
You'll need to think about permissions: when wc.db is rewritten, or a new .svn/pristine/ file created, would user2 have permissions to replace or unlink it (respectively)? Authz would be a concern too, if the two users' read accesses differ. (the code should DTRT --- it's no different than the server revoking some read access in a one-user scenario) > Can someone give more detailed information if the above assumption is > right or wrong ? I assume it's right... Have you considered other solutions? For example, the ASF CMS maintains one working copy per project, and uses zfs copy-on-write clones to fork off a per-user working copy for each user (even concurrent users) who works on that working copy. https://svn.apache.org/repos/infra/websites/cms/webgui/lib/ASF/CMS.pm