Mercurial > hg > orthanc

changeset 6393:bd78776b99b0

Find changesets by keywords (author, files, the commit message), revision number or hash, or revset expression.
fix spelling of Rest API as REST API
author Sebastien Jodogne <s.jodogne@gmail.com>
date Wed, 12 Nov 2025 13:23:14 +0100
parents c6a9ec58d8d1
children e0df58ca5fa5
files OrthancServer/OrthancExplorer/explorer.js TODO
diffstat 2 files changed, 3 insertions(+), 3 deletions(-) [+]
line wrap: on
line diff
--- a/OrthancServer/OrthancExplorer/explorer.js	Wed Nov 12 13:15:55 2025 +0100
+++ b/OrthancServer/OrthancExplorer/explorer.js	Wed Nov 12 13:23:14 2025 +0100
@@ -173,8 +173,8 @@
 
 var authorizationTokens = GetAuthorizationTokensFromUrl();
 
-/* Copy the authoziation toekn from the url search parameters into HTTP headers in every request to the Rest API.  
-Thanks to this behaviour, you may specify a ?token=xxx in your url and this will be passed 
+/* Copy the authoziation token from the url search parameters into HTTP headers in every request to the REST API.
+Thanks to this behaviour, you may specify a ?token=xxx in your url and this will be passed
 as the "token" header in every request to the API allowing you to use the authorization plugin */
 $.ajaxSetup(
   {
--- a/TODO	Wed Nov 12 13:15:55 2025 +0100
+++ b/TODO	Wed Nov 12 13:23:14 2025 +0100
@@ -267,7 +267,7 @@
 * (3) Check out rapidjson: https://github.com/miloyip/nativejson-benchmark
 
 * Long-shot & not sure it is even feasible at all: try to reduce memory usage by implementing streaming
-  when receiving DICOM instances from the Rest API or from DICOM and store files directly to disk as they
+  when receiving DICOM instances from the REST API or from DICOM and store files directly to disk as they
   are received.  Note that this would likely require rewriting large parts of Orthanc.  Note sure that 
   would be compatible with Transcoding.
   Use case: receiving 10 1GB instances in parallel can consume up to 20 GB