Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
There are four common protocols for network access of SVN.
svn://repos
svn+ssh://repos
https://repos
http://repos
The Wikipedia page doesn’t say much about the differences of the four different protocols. I’ve always preferred svn://, because it is the easiest to set up, but what is the difference and which one is “better”?
http://has a serious overhead, especially when dealing with thousands of small files. I used svn for a website that had around 50,000 icons, all saved in SVN. With HTTP, it took around 20 minutes to checkout. Once I switched tosvn://, it took less than a minute. This is because with HTTP it’s one new HTTP request per file.http://however has the following big advantage: it usually goes through firewalls. For example, now that I switched tosvn://I can no longer access my repository from my university because of their firewall.Regarding the difference between using SSL/TLS or not, well, it’s obvious: data is encrypted; however it’s more difficult to set up.