comparison 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
comparison
equal deleted inserted replaced
2931:89f2c302fc37 2932:00504dcc996f
412 }, 412 },
413 413
414 // Whether to run DICOM C-Move operations synchronously. If set to 414 // Whether to run DICOM C-Move operations synchronously. If set to
415 // "false" (the default), each incoming C-Move request results in 415 // "false" (the default), each incoming C-Move request results in
416 // creating a new background job. Up to Orthanc 1.3.2, the implicit 416 // creating a new background job. Up to Orthanc 1.3.2, the implicit
417 // behavior was to use synchronous C-Move. 417 // behavior was to use synchronous C-Move. Between Orthanc 1.4.0 and
418 "SynchronousCMove" : false, 418 // 1.4.2, the default behavior was set to asynchronous C-Move. Since
419 // Orthanc 1.4.3, the default behavior is synchronous C-Move
420 // (backward compatibility with Orthanc <= 1.3.2).
421 "SynchronousCMove" : true,
419 422
420 // Maximum number of completed jobs that are kept in memory. A 423 // Maximum number of completed jobs that are kept in memory. A
421 // processing job is considered as complete once it is tagged as 424 // processing job is considered as complete once it is tagged as
422 // "Success" or "Failure". 425 // "Success" or "Failure".
423 "JobsHistorySize" : 10, 426 "JobsHistorySize" : 10,