Changes between Version 1 and Version 3 of Ticket #3777


Ignore:
Timestamp:
2021-08-23T15:27:41Z (3 years ago)
Author:
itamarst
Comment:

Legend:

Unmodified
Added
Removed
Modified

  • Ticket #3777 – Description

    v1 v3  
    2222Fifth, taking a step back and looking at the big picture, I am not certain that supporting reading from multiple shares (or more broadly, reading multiple chunks) in a single query is actually useful.
    2323
    24 1. It's not clear to me it simplifies the client implementation.
    25 2. There are API design difficulties of receive arbitrarily sized multiple chunks in a single stream.
     241. It's not clear to me it simplifies the client implementation. Clients can just send multiple HTTP requests in parallel.
     252. There are Python API design difficulties of receive arbitrarily sized multiple chunks in a single stream.
    26263. Using single CBOR result streaming isn't really easy to support. Alternative is to concatenate multiple separately CBOR-encoded values (i.e. writing multiple results of `cbor2.dumpb` or whatever), which CBOR libraries can handle better.
    27274. Given support for parallel requests, it doesn't improve latency (though it does have minor reduction in bandwidth usage).