Mercurial > hg > orthanc-book
changeset 1002:6b959b4823aa
note about stable resources
author | Sebastien Jodogne <s.jodogne@gmail.com> |
---|---|
date | Wed, 20 Dec 2023 07:52:29 +0100 |
parents | 56da617938f0 |
children | 5c7838bfb18d |
files | Sphinx/source/faq/scalability.rst |
diffstat | 1 files changed, 9 insertions(+), 5 deletions(-) [+] |
line wrap: on
line diff
--- a/Sphinx/source/faq/scalability.rst Tue Dec 19 17:54:53 2023 +0100 +++ b/Sphinx/source/faq/scalability.rst Wed Dec 20 07:52:29 2023 +0100 @@ -337,6 +337,10 @@ the ``/jobs`` route will return only the jobs of the responding Orthanc. + - Similarly, each Orthanc instance maintains its own :ref:`status + for the resources it has received <stable-resources>`. Thus, the + ``IsStable`` information is local to each Orthanc instance. + - The ``/modalities`` or the ``/peers`` are also private to each instance of Orthanc in the cluster, as soon as the respective options ``DicomModalitiesInDatabase`` and @@ -345,11 +349,11 @@ If you need to use such primitives in your application, you have three possibilities: (1) Introduce a distinguished Orthanc server that is responsible to take care of all the jobs (including - modalities and peers), (2) create an :ref:`Orthanc plugin <plugins>` - (e.g. using :ref:`Python <python-plugin>` or :ref:`Java - <java-plugin>`) that queries all the Orthanc in the cluster and that - aggregates all of their answers, or (3) do the same using a - higher-level framework (such as Node.js). + modalities and peers) and/or to receive all the DICOM instances, (2) + create an :ref:`Orthanc plugin <plugins>` (e.g. using :ref:`Python + <python-plugin>` or :ref:`Java <java-plugin>`) that queries all the + Orthanc in the cluster and that aggregates all of their answers, + or (3) do the same using a higher-level framework (such as Node.js). Latency