Mercurial > hg > orthanc-transfers
comparison NEWS @ 45:f633b835c5bd
doc
author | Alain Mazy <am@osimis.io> |
---|---|
date | Thu, 20 Oct 2022 09:28:37 +0200 |
parents | f4e828607f02 |
children | 155eec0d4d3b |
comparison
equal
deleted
inserted
replaced
44:f4e828607f02 | 45:f633b835c5bd |
---|---|
3 | 3 |
4 * new "SenderTransferID" option when creating a transfer. This id is added as an HTTP Header | 4 * new "SenderTransferID" option when creating a transfer. This id is added as an HTTP Header |
5 ("sender-transfer-id") in every outgoing request that relates to this transfer and can be used | 5 ("sender-transfer-id") in every outgoing request that relates to this transfer and can be used |
6 e.g, by a load balancer to route all requests from a single transfer to the same Orthanc. | 6 e.g, by a load balancer to route all requests from a single transfer to the same Orthanc. |
7 If no "SenderTransferID" is provided, a UUID is generated by the plugin. This header is only | 7 If no "SenderTransferID" is provided, a UUID is generated by the plugin. This header is only |
8 used in PushMode | 8 used in PushMode. |
9 Note that, when generated by the plugin, the "sender-transfer-id" is NOT the job id (the job id | |
10 does not exists yet at this time) and is NOT the transaction id that is actually generated on the | |
11 receiver side. | |
9 | 12 |
10 Version 1.2 (2022-07-12) | 13 Version 1.2 (2022-07-12) |
11 ======================== | 14 ======================== |
12 | 15 |
13 => Minimum SDK version: 1.5.0 <= | 16 => Minimum SDK version: 1.5.0 <= |