Talden wrote:
>
>> point taken Ryan, we'll certainly consider changing to svnserve. we
>> don't want anyone to delete the repository :(
>>
>> i do appreciate all the concern for my environment but any chance
>> someone can answer my actual question, namely what weird things can
>> happen with file:/// ? I'm just interested to know what the mechanics
>> of this are. is the only issue that file:/// leaves the repos wide
>> open for deletion on the file-system?
>>
>> thx again.
>
> I'd say Andy answered that quite clearly already. I expect that
> 'weird' in this context would extend to any number of non-synchonised
> concurrency issues. Andy has clearly expressed the risk of corruption
> but I expect you can also get broken updates/checkouts by doing so
> while another user is writing.
Assuming the OS file locking works, the concurrency issues should be
handled correctly - but that's a big assumption, especially if you have
a mix of OS's across the clients and file server. Using svn: and http:
access will have the same concurrency issues but everything is on the
same OS.
--
Les Mikesell
lesmikesell_at_gmail.com
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe_at_subversion.tigris.org
For additional commands, e-mail: users-help_at_subversion.tigris.org
Received on 2008-02-26 01:03:15 CET