# HG changeset patch
# User Sebastien Jodogne <s.jodogne@gmail.com>
# Date 1703055149 -3600
# Node ID 6b959b4823aacd7ec144b49f62e4a1f2656c608a
# Parent  56da617938f0a0eb30e69e322b284838c11ce987
note about stable resources

diff -r 56da617938f0 -r 6b959b4823aa Sphinx/source/faq/scalability.rst
--- 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