[svnbook commit] r2947 - trunk/src/en/book

sussman noreply at red-bean.com
Mon Dec 17 23:11:11 CST 2007


Author: sussman
Date: Mon Dec 17 23:11:02 2007
New Revision: 2947

Log:
* ch06:  stop mentioning Neon over and over, keep it vague-er.

Modified:
   trunk/src/en/book/ch06-server-configuration.xml

Modified: trunk/src/en/book/ch06-server-configuration.xml
==============================================================================
--- trunk/src/en/book/ch06-server-configuration.xml	(original)
+++ trunk/src/en/book/ch06-server-configuration.xml	Mon Dec 17 23:11:02 2007
@@ -2816,30 +2816,31 @@
         <para>Several of the features already provided by Apache in
           its role as a robust Web server can be leveraged for
           increased functionality or security in Subversion as well.
-          Subversion communicates with Apache using Neon, which is a
-          generic HTTP/WebDAV library with support for such mechanisms
-          as SSL (the Secure Socket Layer, discussed earlier).  If
-          your Subversion client is built to support SSL, then it can
-          access your Apache server
-          using <literal>https://</literal>.</para>
+          The Subversion client is able to use SSL, (the Secure Socket
+          Layer, discussed earlier).  If your Subversion client is
+          built to support SSL, then it can access your Apache server
+          using <literal>https://</literal> and enjoy a high-quality
+          encrypted network session.</para>
 
         <para>Equally useful are other features of the Apache and
           Subversion relationship, such as the ability to specify a
           custom port (instead of the default HTTP port 80) or a
           virtual domain name by which the Subversion repository
           should be accessed, or the ability to access the repository
-          through an HTTP proxy.  These things are all supported by
-          Neon, so Subversion gets that support for free.</para>
+          through an HTTP proxy.</para>
 
         <para>Finally, because <command>mod_dav_svn</command> is
           speaking a subset of the WebDAV/DeltaV protocol, it's
           possible to access the repository via third-party DAV
           clients.  Most modern operating systems (Win32, OS X, and
           Linux) have the built-in ability to mount a DAV server as a
-          standard network share.  This is a complicated topic; for
+          standard network <quote>shared folder</quote>.  This is a
+          complicated topic, but also wondrous when implemented.  For
           details, read <xref linkend="svn.webdav"/>.</para>
 
-        <para>For a complete list of
+        <para>Note that there are number of other small tweaks one can
+          make to <command>mod_dav_svn</command> that are too obscure
+          to mention in this chapter.  For a complete list of
           all <filename>httpd.conf</filename> directives
           that <command>mod_dav_svn</command> responds to, see
           <xref linkend="svn.ref.mod_dav_svn.conf.directives"/>.</para>




More information about the svnbook-dev mailing list