# HG changeset patch # User Sebastien Jodogne # Date 1620043899 -7200 # Node ID bc8fa2bf4cf7bc2b9d643a58ea1f8af1ee58fb7b # Parent f32934bdad14dd0c5b6cec8cd99434fed0ba8b98 asynchronous c-move diff -r f32934bdad14 -r bc8fa2bf4cf7 Sphinx/source/users/advanced-rest.rst --- a/Sphinx/source/users/advanced-rest.rst Mon May 03 12:43:28 2021 +0200 +++ b/Sphinx/source/users/advanced-rest.rst Mon May 03 14:11:39 2021 +0200 @@ -136,6 +136,11 @@ calls), waiting for the ``State`` field to become ``Success`` or ``Failure``. +Note that the `integration tests of Orthanc +`__ +give an example about how to monitor a job in Python using the REST +API (cf. function ``MonitorJob()``). + .. _jobs-controlling: diff -r f32934bdad14 -r bc8fa2bf4cf7 Sphinx/source/users/rest.rst --- a/Sphinx/source/users/rest.rst Mon May 03 12:43:28 2021 +0200 +++ b/Sphinx/source/users/rest.rst Mon May 03 14:11:39 2021 +0200 @@ -853,8 +853,8 @@ $ curl --request POST --url http://localhost:8042/queries/5af318ac-78fb-47ff-b0b0-0df18b0588e0/answers/0/retrieve --data Orthanc If C-Moves take too long (for example, performing a C-Move of a big -study), you may run the request in asynchronous fashion, which will -create a job in Orthanc:: +study), you may run the request in :ref:`asynchronous mode `, +which will create a job in Orthanc:: $ curl --request POST --url http://localhost:8042/queries/5af318ac-78fb-47ff-b0b0-0df18b0588e0/retrieve \ --data '{"TargetAet":"Orthanc","Synchronous":false}' @@ -862,7 +862,9 @@ .. highlight:: bash -The answer of this POST request is the job ID taking care of the C-Move:: +The answer of this POST request is the job ID taking care of the +C-Move command, :ref:`whose status can be monitored ` +in order to detect failure or completion:: { "ID" : "11541b16-e368-41cf-a8e9-3acf4061d238",