svn commit: r1702217 - /subversion/site/publish/docs/release-notes/1.9.html

[ph...@apache.org]

Author: philip
Date: Thu Sep 10 11:13:50 2015
New Revision: 1702217

URL: http://svn.apache.org/r1702217
Log:
* docs/release-notes/1.9.html
  Add #lock-http-pipelining and #locking-multiple-files.

Modified:
    subversion/site/publish/docs/release-notes/1.9.html

Modified: subversion/site/publish/docs/release-notes/1.9.html
URL: http://svn.apache.org/viewvc/subversion/site/publish/docs/release-notes/1.9.html?rev=1702217&r1=1702216&r2=1702217&view=diff
==============================================================================
--- subversion/site/publish/docs/release-notes/1.9.html (original)
+++ subversion/site/publish/docs/release-notes/1.9.html Thu Sep 10 11:13:50 2015
@@ -112,6 +112,24 @@ and what impact these changes may have.<
     <td>1.9</td>
     <td>Older formats remain supported.</td></tr>
   <tr>
+    <td><a href="#lock-http-pipelining">Lock HTTP pipelining</a></td>
+    <td>1.9</td>
+    <td>1.2</td>
+    <td>1.2</td>
+    <td></td></tr>
+  <tr>
+    <td><a href="#locking-multiple-files">Commit unlocking</a></td>
+    <td>1.2</td>
+    <td>1.9</td>
+    <td>1.2</td>
+    <td></td></tr>
+  <tr>
+    <td><a href="#locking-multiple-files">Locking multiple files</a></td>
+    <td>1.3</td>
+    <td>1.9</td>
+    <td>1.2</td>
+    <td>Over the svn:// protocol.</td></tr>
+  <tr>
     <td><a href="#FSX">FSX</a></td>
     <td>any</td>
     <td>1.9</td>
@@ -1318,6 +1336,47 @@ command can determine the revision in wh
 
 </div> <!-- prospective-blame -->
 
+<div class="h3" id="lock-http-pipelining">
+<h3>Lock HTTP pipelining
+  <a class="sectionlink" href="#lock-http-pipelining"
+     title="Link to this section">&para;</a>
+</h3>
+
+<p>When locking, or unlocking, multiple files in a single operation
+over HTTP the client will use HTTP pipelining for the individual
+WebDAV LOCK and UNLOCK requests.  This makes the operation faster
+particularly on connections with large network latency.  While HTTP
+pipelining is new for LOCK and UNLOCK the client was already using it
+for GET requests.</p>
+
+</div> <!-- lock-http-pipelining -->
+
+<div class="h3" id="locking-multiple-files">
+<h3>Locking Multiple Files
+  <a class="sectionlink" href="#locking-multiple-files"
+     title="Link to this section">&para;</a>
+</h3>
+
+<p>Subversion locks, the locks that prevent commits from other working
+copies, are stored in the repository. When adding or removing locks
+the FSFS backend can now operate on several locks at once.  This
+reduces the amount of disk IO when handling multiple locks and is
+significant when the total number of locks in the repository is large,
+100,000 say.</p>
+
+<p>The default behaviour for commits is to automatically release locks
+after a successful commit and this takes advantage of the more
+efficient lock process.  In previous versions the disk IO involved in
+releasing the locks would sometimes be greater than that involved in
+creating the new revision.</p>
+
+<p>Clients using the svn:// protocol will also benefit from the more
+efficient lock handling when locking or unlocking multiple files in a
+single operation.  Clients using HTTP will not get this benefit since
+the client still sends multiple LOCK and UNLOCK requests.</p>
+
+</div> <!-- locking-multiple-files -->
+
 </div>  <!-- enhancements -->
 
 <div class="h2" id="issues">