Mercurial > hg > orthanc

changeset 2932:00504dcc996f

Find changesets by keywords (author, files, the commit message), revision number or hash, or revset expression.
"SynchronousCMove" is now "true" by default
author Sebastien Jodogne <s.jodogne@gmail.com>
date Thu, 15 Nov 2018 11:35:35 +0100
parents 89f2c302fc37
children 2dfa40b9ca42 aeeb40a35ce1
files NEWS OrthancServer/OrthancMoveRequestHandler.cpp Resources/Configuration.json
diffstat 3 files changed, 7 insertions(+), 3 deletions(-) [+]
line wrap: on
line diff
--- a/NEWS	Tue Nov 13 17:50:03 2018 +0100
+++ b/NEWS	Thu Nov 15 11:35:35 2018 +0100
@@ -26,6 +26,7 @@
 Maintenance
 -----------
 
+* "SynchronousCMove" is now "true" by default
 * New modality manufacturer: "GE" for GE Healthcare EA and AW
 * Executing a query/retrieve from the REST API now creates a job
 * Fix: Closing DICOM associations after running query/retrieve from REST API
--- a/OrthancServer/OrthancMoveRequestHandler.cpp	Tue Nov 13 17:50:03 2018 +0100
+++ b/OrthancServer/OrthancMoveRequestHandler.cpp	Thu Nov 15 11:35:35 2018 +0100
@@ -238,7 +238,7 @@
                                               const std::string& originatorAet,
                                               uint16_t originatorId)
   {
-    bool synchronous = Configuration::GetGlobalBoolParameter("SynchronousCMove", false);
+    bool synchronous = Configuration::GetGlobalBoolParameter("SynchronousCMove", true);
 
     if (synchronous)
     {
--- a/Resources/Configuration.json	Tue Nov 13 17:50:03 2018 +0100
+++ b/Resources/Configuration.json	Thu Nov 15 11:35:35 2018 +0100
@@ -414,8 +414,11 @@
   // 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.
-  "SynchronousCMove" : false,
+  // 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.4.3, the default behavior is synchronous C-Move
+  // (backward compatibility with Orthanc <= 1.3.2).
+  "SynchronousCMove" : true,
 
   // Maximum number of completed jobs that are kept in memory. A
   // processing job is considered as complete once it is tagged as