Mercurial > hg > orthanc
diff Resources/Configuration.json @ 2932:00504dcc996f
"SynchronousCMove" is now "true" by default
author | Sebastien Jodogne <s.jodogne@gmail.com> |
---|---|
date | Thu, 15 Nov 2018 11:35:35 +0100 |
parents | 87366b8aed4f |
children | 2e751f615e03 |
line wrap: on
line diff
--- 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