On Thu, Jul 29, 2010 at 16:40, David Weintraub <qazw...@gmail.com> wrote: > On Thu, Jul 29, 2010 at 4:59 AM, STF SVN <lapsap7+...@gmail.com> wrote: >> I already have a working SVN server using HTTP, but I'd like to see >> some other alternatives, especially those which could provide better >> performance. The problem right now is that some users are accessing >> the SVN within a VPN tunnel and things are slow for them. So, if it's >> possible to reduce data quantity, like using another protocol, I would >> take it. > > The standard 'svn' protocol is faster, but it uses port 3690 by > default. It is very likely that your VPN will block traffic to this > port. You can start svnserve on another port, and you can use ssh+svn > which allows for tunneling. > > Subversion is known for simplicity, ease of use, but speed isn't one > of them. The entire .svn directory thing slows Subversion down -- > especially since the entire diff is kept in there. > > I believe you can have a Subversion repository run using both the > svn:// protocol and the http:// protocol at the same time (Is this > true? Somebody respond).
True. http://svnbook.red-bean.com/nightly/en/svn.serverconfig.multimethod.html