title: Why choose mod_dav_svn instead of svnserve & a repository browser?
body: <p>Please correct me if I am wrong about my understanding of mod_dav_svn, which is that it basically serves 2 purposes:</p>
  
  <ol>
  <li>Expose the SVN repository (on the filesystem) to clients, which can be either:
  <ul>
  <li>repository browsers (e.g. web)</li>
  <li>the 'svn' command itself, which is a client command line program</li>
  </ul></li>
  <li>Act as a repository browser to make the repository viewable in a convenient way</li>
  </ol>
  
  <p>Now for point 1, are my following assumptions correct?</p>
  
  <ul>
  <li>Anytime a repository is exposed using mod_dav_svn, the <strong>http://</strong> or <strong>https://</strong> form of accessing the repository is used</li>
  <li>If using svnserve, the <strong>svn://</strong> form of accessing the repository is used
  <ul>
  <li>In this case, mod_dav_svn would <strong>serve no additional use</strong></li>
  </ul></li>
  </ul>
  
  <p>For point 2, if using Trac's repository browsing functionality, there is no additional use for the repository browsing functionality offered by mod_dav_svn?</p>
  
  <p>Does mod_dav_svn serve any other purpose I haven't outlined here? Asked another way, is there any disadvantage to going with svnserve and Trac?</p>
  
  <p>I ask because I get the impression that mod_dav_svn is very commonly used, so I wonder what I'm missing.</p>