• PS 3.18: multipart/related vs HTTP2

    From Mathieu Malaterre@21:1/5 to All on Fri Mar 26 09:07:41 2021
    As far as I understand WADO-RS was designed and implemented in HTTP1.1 world.

    So to allow a user to download multiple frames using a single connection there was only one solution: multipart/related.

    $ curl --header "Accept: multipart/related; type=image/jls" "http://acme.corp/dicom-web/studies/1.2.3/series/4.5.6/instances/7.8.9/frames/1,2,3,4,5,6,7,8,9" -o frames.part -v

    Does the above solution still make sense when HTTP2 is becoming more and more available ? Unless I am missing a scenario, the above should be just as efficient as:

    $ printf 'remote-name\nurl = "http://acme.corp/dicom-web/studies/1.2.3/series/4.5.6/instances/7.8.9/frames/%s"\n' $(seq 1 9) > frames.txt
    $ curl -sS --http2-prior-knowledge -Z -K frames.txt

    This simplifies the implementation both on the server side as well as on the client side: no need to encapsulate/de-encapsulate the binary pixel frame inside a multipart/related message.

    Is it time for Supplement ? or did I miss one use-case ?

    Thanks for comments,

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)