Hi,
> 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...
so after thinking about the concept...
it does not make sense to go further with a shared working copies on a
network drive there are too many issues (of course, cause SVN is not
made for such things)..so i will drop the idea...
Thanks for clearing up...
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
Does this solutions supports having different working copies per user
which can access them or are these working copies on a per project base?
What about locking of files in the working copy (svn:needs-lock) etc. ?
How could they be accessed ?
Furthermore i have started to think about WebDav (after a hint of a
colleague of mine) might be a solution on Windows, but i don't know how
WebDav behave if two people working on the same file and saving the
file? What about conflicts? What about locking of files ?
Kind regards
Karl-Heinz Marbaise
--
SoftwareEntwicklung Beratung Schulung Tel.: +49 (0) 2405 / 415 893
Dipl.Ing.(FH) Karl-Heinz Marbaise ICQ#: 135949029
Hauptstrasse 177 USt.IdNr: DE191347579
52146 Würselen http://www.soebes.de
