title: Is it feasible to use svn for documents
body: <p>We need to have documents shared between clients (CRM-like functionality). Users need to be able to:</p>
  
  <ul>
  <li>Edit the documents and save them again</li>
  <li>Attach new documents</li>
  </ul>
  
  <p>Our application is coded in WPF with WCF for data-transport and NHibernate/SQL for data on the server.</p>
  
  <p>what we're thinking is to use SVN and have the app create a local check-out of parts of the repository (when they click a document, it is checked out by SVN in the background and opened from the local path) - When saved it will silently (using monitoring of the path) be committed back to the repository.</p>
  
  <p>Question: Is this feasible - or are there better solutions to this?</p>
  
  <p>EDIT 1: 
  Summary so far: </p>
  
  <ul>
  <li>I'll look into using Git/Mercurial instead of SVN</li>
  <li>Document size (revisions) might be prohibitive pending tests</li>
  <li>SharePoint is an option (although not viable in my case as the cost alone is prohibitive) - I will look into the alternatives for SharePoint, tho.</li>
  <li>Not much experience out there about using repositories for many users although it works for small teams..</li>
  <li>Wiki software might be an alternative to SVN.</li>
  </ul>
  
  <p>Thanks for all the feedback - I'll keep it open a bit longer.</p>
  
  <p>EDIT 2:
  Summary after a few days of work - I have a client working - see my progress <a href="http://goblincave.net/10/2010/developing-a-light-weight-distributed-document-library.php" rel="nofollow">here</a>.</p>