Mercurial > hg > orthanc-book

comparison Sphinx/source/faq/features.rst @ 672:8bda16db46cf

Find changesets by keywords (author, files, the commit message), revision number or hash, or revset expression.
SynchronousCMove: Synchronous vs. asynchronous C-MOVE SCP
author Sebastien Jodogne <s.jodogne@gmail.com>
date Mon, 03 May 2021 14:31:42 +0200
parents 36bf58dfb7f7
children 9c23356b9464
comparison
equal deleted inserted replaced
671:bc8fa2bf4cf7 672:8bda16db46cf
416 of the REST API of Orthanc for more information. 416 of the REST API of Orthanc for more information.
417 417
418 **Warning:** The database index back-end must support revisions. As of 418 **Warning:** The database index back-end must support revisions. As of
419 writing, only the **PostgreSQL plugin** in versions above 4.0 419 writing, only the **PostgreSQL plugin** in versions above 4.0
420 implement support for revisions. 420 implement support for revisions.
421
422
423 Synchronous vs. asynchronous C-MOVE SCP
424 ---------------------------------------
425
426 The :ref:`C-MOVE SCP <dicom-move>` of Orthanc (i.e. the component of
427 the Orthanc server that is responsible for routing DICOM instances
428 from Orthanc to other modalities) can be configured to run either in
429 synchronous or in asynchronous mode, depending on the value of the
430 ``SynchronousCMove`` :ref:`configuration option <configuration>`:
431
432 * In **synchronous mode** (if ``SynchronousCMove`` is ``true``),
433 Orthanc will interleave its C-STORE SCU commands with the C-MOVE
434 instructions received from the remote modality. In other words,
435 Orthanc immediately sends the DICOM instances while it handles the
436 C-MOVE command from the remote modality. This mode is for
437 compatibility with simple DICOM client software that considers that
438 when its C-MOVE SCU is over, it should have received all the
439 instructed DICOM instances. This is the default behavior of Orthanc.
440
441 * In **asynchronous mode** (if ``SynchronousCMove`` is ``false``),
442 Orthanc will queue the C-MOVE instructions and :ref:`creates a job
443 <jobs-synchronicity>` that will issue the C-STORE SCU commands
444 afterward. This behavior is typically encountered in hospital-wide
445 PACS systems, but requires the client software to be more complex as
446 it must be handle the delay between its C-MOVE queries and the
447 actual reception of the DICOM instances through C-STORE.
448
449 As a consequence, by setting ``SynchronousCMove`` to ``true``, Orthanc
450 can be used as a buffer that enables communications between a simple
451 C-MOVE client and a hospital-wide PACS. This can be interesting to
452 introduce compatibility with specialized image processing
453 applications.