Experience with concurrent Subversion repository access modules

We're looking at moving our repository access from svnserve to apache/Subversion Edge to enable easier administration, transport level encryption and windows authentication.

I've read several times that, assuming the processes are run as the same users, or at least with the same permissions, Subversio开发者_运维技巧n supports concurrent repository access with different modules (ra_svn, ra_serf, etc.).

My question: has anyone had real-life experience with this in a production environment? If so, did you experience any issues? Our Subversion server has ~60 users, including issue tracker and build server, so we have a bit of traffic and rely on svn running smoothly (as per usual).

Please note that I'm interested in hearing from developers as well as admins, otherwise I would've asked on serverfault, thanks :)

---

I deployed and used SVN with Apache and used windows authentication as described in the manual of SVN and it was working great except for one issue that when committing large number of files it fails with Authentication failed error. Developers had to commit their changes in batches of 20 to 30 files. When first committing a large project I (the admin) used to do it from the server machine to be able to use file:// instead of https:// to access the repository as the problem only happens when accessing via HTTP.

I have searched for solutions for this problem and did not find a solution if any one knows about that it would be very helpful to tell us.

I do not know about ra_svn & ra_serf.

---

For those wishing to try, our company successfully migrated svnserve to Subversion Edge. The two Subversion servers, running as different services on the same box, were used concurrently for just over a week and we didn't hit any issues.

Whilst I still don't know whether this is officially supported, our experience was good :)