# HG changeset patch
# User Sebastien Jodogne <s.jodogne@gmail.com>
# Date 1545315895 -3600
# Node ID 095193bbd7b9ff6df6fcd463f6f5fc2af4fb87ab
# Parent  1000178f94e485a7c66ec9ef8652aa3ed0a75640
fix issue #118

diff -r 1000178f94e4 -r 095193bbd7b9 NEWS
--- a/NEWS	Thu Dec 20 12:22:49 2018 +0100
+++ b/NEWS	Thu Dec 20 15:24:55 2018 +0100
@@ -1,6 +1,10 @@
 Pending changes in the mainline
 ===============================
 
+Maintenance
+-----------
+
+* Fix issue #118 (Wording in Configuration.json regarding SynchronousCMove)
 
 
 Version 1.5.1 (2018-12-20)
diff -r 1000178f94e4 -r 095193bbd7b9 Resources/Configuration.json
--- a/Resources/Configuration.json	Thu Dec 20 12:22:49 2018 +0100
+++ b/Resources/Configuration.json	Thu Dec 20 15:24:55 2018 +0100
@@ -412,12 +412,13 @@
   },
 
   // Whether to run DICOM C-Move operations synchronously. If set to
-  // "false" (the default), each incoming C-Move request results in
-  // creating a new background job. Up to Orthanc 1.3.2, the implicit
-  // behavior was to use synchronous C-Move. Between Orthanc 1.4.0 and
-  // 1.4.2, the default behavior was set to asynchronous C-Move. Since
-  // Orthanc 1.5.0, the default behavior is synchronous C-Move
-  // (backward compatibility with Orthanc <= 1.3.2).
+  // "false" (asynchronous mode), each incoming C-Move request results
+  // in the creation of a new background job. Up to Orthanc 1.3.2, the
+  // implicit behavior was to use synchronous C-Move ("true"). Between
+  // Orthanc 1.4.0 and 1.4.2, the default behavior was set to
+  // asynchronous C-Move ("false"). Since Orthanc 1.5.0, the default
+  // behavior is back to synchronous C-Move ("true", which ensures
+  // backward compatibility with Orthanc <= 1.3.2).
   "SynchronousCMove" : true,
 
   // Maximum number of completed jobs that are kept in memory. A