changeset 854:b569e93d1d45

jobs update
author Alain Mazy <am@osimis.io>
date Wed, 08 Jun 2022 16:35:11 +0200
parents 2d9024137da0
children 12f8932ee3a7
files Sphinx/source/users/advanced-rest.rst
diffstat 1 files changed, 8 insertions(+), 5 deletions(-) [+]
line wrap: on
line diff
--- a/Sphinx/source/users/advanced-rest.rst	Fri Jun 03 15:12:41 2022 +0200
+++ b/Sphinx/source/users/advanced-rest.rst	Wed Jun 08 16:35:11 2022 +0200
@@ -17,7 +17,9 @@
 ----
 
 Since Orthanc 1.4.0, a jobs engine is embedded within Orthanc. Jobs
-are high-level tasks to be processed by Orthanc. Jobs are first added
+are high-level tasks to be processed by Orthanc. Jobs can be started
+synchronously or asynchronously (see the section below).  All Jobs,
+no matter how they were started, are first added
 to a queue of pending tasks, and Orthanc will simultaneously execute a
 fixed number of jobs (check out :ref:`configuration option
 <configuration>` ``ConcurrentJobs``). Once the jobs have been
@@ -27,10 +29,11 @@
 
 By default, Orthanc saves the jobs into its database (check out the
 ``SaveJobs`` option).  Jobs are saved every 10 seconds and when
-Orthanc stops. If Orthanc is stopped then relaunched, the jobs
-whose processing was not finished are automatically put into the queue
-of pending tasks or resumed if they were being processed when Orthanc
-stopped. The command-line option ``--no-jobs`` can also be used to 
+Orthanc stops. If Orthanc is stopped then relaunched, the jobs whose 
+processing was not finished are automatically put into the queue of 
+pending tasks or resumed if they were being processed when Orthanc stopped, 
+regardless of whether they were started synchronously or asynchronously 
+(see the section below). The command-line option ``--no-jobs`` can also be used to 
 prevent the loading of jobs from the database upon the launch of 
 Orthanc.