comparison Sphinx/source/plugins/dicomweb.rst @ 325:c94074bbf7aa

note about issue #156
author Sebastien Jodogne <s.jodogne@gmail.com>
date Tue, 03 Mar 2020 16:43:53 +0100
parents 89d4ee2e6e6e
children 011b01ccf52d
comparison
equal deleted inserted replaced
324:89d4ee2e6e6e 325:c94074bbf7aa
287 server does not support `HTTP chunked transfer encoding 287 server does not support `HTTP chunked transfer encoding
288 <https://en.wikipedia.org/wiki/Chunked_transfer_encoding>`__. Setting 288 <https://en.wikipedia.org/wiki/Chunked_transfer_encoding>`__. Setting
289 this option to ``true`` is the best choice to reduce memory 289 this option to ``true`` is the best choice to reduce memory
290 consumption. However, it must be set to ``false`` if the remote 290 consumption. However, it must be set to ``false`` if the remote
291 DICOMweb server is Orthanc <= 1.5.6, as chunked transfer encoding is 291 DICOMweb server is Orthanc <= 1.5.6, as chunked transfer encoding is
292 only supported starting with Orthanc 1.5.8. Beware setting ``ChunkedTransfers`` 292 only supported starting with Orthanc 1.5.7. Beware setting
293 to ``true`` utilizes all CPU resources which results in extremely low throughput 293 ``ChunkedTransfers`` to ``true`` in Orthanc 1.5.7 and 1.5.8 utilizes
294 as of version 1.0 of the DICOMweb plugin (see 294 one CPU at 100%, which results in very low throughput: This issue is
295 `issue 156 <https://bitbucket.org/sjodogne/orthanc/issues/156/>`__ for status). 295 resolved in Orthanc 1.6.0 (cf. `issue 156
296 <https://bitbucket.org/sjodogne/orthanc/issues/156/>`__ for full
297 explanation).
296 298
297 * ``HasWadoRsUniversalTransferSyntax`` (new in DICOMweb 1.1) must be 299 * ``HasWadoRsUniversalTransferSyntax`` (new in DICOMweb 1.1) must be
298 set to ``false`` if the remote DICOMweb server does not support the 300 set to ``false`` if the remote DICOMweb server does not support the
299 value ``transfer-syntax=*`` in the ``Accept`` HTTP header for 301 value ``transfer-syntax=*`` in the ``Accept`` HTTP header for
300 WADO-RS requests. This option is notably needed if the remote 302 WADO-RS requests. This option is notably needed if the remote