Author: stsp Date: Wed Aug 17 08:11:35 2011 New Revision: 1158561 URL: http://svn.apache.org/viewvc?rev=1158561&view=rev Log: * publish/docs/release-notes/1.7.html: Update information about serf.
Modified: subversion/site/publish/docs/release-notes/1.7.html Modified: subversion/site/publish/docs/release-notes/1.7.html URL: http://svn.apache.org/viewvc/subversion/site/publish/docs/release-notes/1.7.html?rev=1158561&r1=1158560&r2=1158561&view=diff ============================================================================== --- subversion/site/publish/docs/release-notes/1.7.html (original) +++ subversion/site/publish/docs/release-notes/1.7.html Wed Aug 17 08:11:35 2011 @@ -115,8 +115,8 @@ via calls to the <code>svn_ra.h</code> i <td>any</td> <td>Permutations of older client/server combinations will continue to function at the pre-1.7 feature level. Server-side configuration - changes might be required for optimal performance (see - <a href="#serf">below</a>).</td></tr> + changes might be required for optimal performance with clients that + use libsvn_ra_serf (see <a href="#serf">below</a>).</td></tr> <tr> <td><a href="#wc-ng">WC-NG</a></td> <td>1.7</td> @@ -501,9 +501,9 @@ materialized.</p> connecting to supported servers. This simpler protocol (sometimes referred to as <em>HTTPv2</em>) requires fewer client-server round trips to establish a connection, making Subversion much more performant on high-latency network -connections. Subversion's Serf-based repository access library (which is -<a href="#serf">now the default</a> library for HTTP use) has received all of -the protocol changes scheduled for 1.7, affecting both commit and read +connections. Subversion's Serf-based repository access library (which will +<a href="#serf">become the default</a> library for HTTP in Subversion 1.8) has received +all of the protocol changes scheduled for 1.7, affecting both commit and read operations; the older Neon-based library has received the most important and high-impact of these changes, too.</p> @@ -862,17 +862,39 @@ for details.</p> </div> <!-- bug-fixes --> <div class="h3" id="serf"> -<h3>Serf now default HTTP library (<em>client</em>) +<h3>Serf HTTP library improved and stabilized (<em>client</em>) <a class="sectionlink" href="#serf" title="Link to this section">¶</a> </h3> -<p><a href="http://code.google.com/p/serf/">serf</a> is now the default library -used for accessing HTTP-based repositories. You can still build and use the -<a href="http://www.webdav.org/neon/">neon</a> library, as you always have, and -configure which library the client should use on -a default or host-by-host basis by setting the <tt>http-library</tt> -variable in the client-side <tt>servers</tt> configuration file +<p>The <code>libsvn_ra_serf</code> repository access library has received +a lot of improvements and stabilization. +The design of <a href="http://code.google.com/p/serf/">serf</a> facilitates +future performance improvements that are impossible to achieve with +<a href="http://www.webdav.org/neon/">neon</a>. There were plans to make +serf the default HTTP access library for the 1.7 release. +But because of some remaining issues (for instance +<a href="http://subversion.tigris.org/issues/show_bug.cgi?id=3979" + >issue #3979</a>, +<a href="http://subversion.tigris.org/issues/show_bug.cgi?id=3980" + >issue #3980</a>, and +<a href="http://subversion.tigris.org/issues/show_bug.cgi?id=3981" + >issue #3981</a>), +Subversion 1.7 still uses libsvn_ra_neon by default. +Remaining problems are mostly due to insufficient infrastructure deployed +in the wild wild web, such as HTTP proxies that do not support HTTP/1.1. +Workarounds for these problems will be implemented for the next release. +serf will become the default HTTP access library in Subversion 1.8. +</p> +<p> +In the meantime, we encourage all users to try serf with Subversion 1.7 and +<a href="/docs/community-guide/issues.html#reporting-bugs" +>report any problems</a>. Successful test reports are appreciated as well. +Tests in networks that use HTTP proxies or enterprise authentication are +particularly helpful. +You can configure which library the client should use on a default or +host-by-host basis by setting the <tt>http-library</tt> variable in the +client-side <tt>servers</tt> configuration file (<tt>~/.subversion/servers</tt>).</p> <div class="notice">