Markus D. Herrmann

Maybe we could implement a `ConcurrentSession` based on *asks*, that implements the same interface of `requests.Session`.

The *requests* documentation recommends a couple of other libraries as well: https://requests.readthedocs.io/en/latest/user/advanced/#blocking-or-non-blocking For example * [httpx](https://github.com/encode/httpx) * [requests-futures](https://github.com/ross/requests-futures)

> Backwards compatibility would not be an issue, at least for us. I am not in favor of breaking the API. We made the call to expose *requests* via the...

> Yes, that's what I meant - a new API would be fine. Sounds great. We can experiment with the different libraries. I defer to your expertise regarding choice of...

So far, we only considered the RESTful Web Services and ignored the URI Web Service. I am not sure whether we should try to integrate both services in the exiting...

cc @cgorman @cpbridge

@chafey the `DICOMwebClient` class is a Python client for interfacing with a DICOMweb server over HTTP. The new `DICOMfileClient` allows users to access DICOM data sets that are stored locally...

> Maybe you could start by taking a similar approach, just use S3 ListObjects API and parse each one to build the master list. After that is done, you can...

I was hoping that we could provide the same functionality for S3 buckets via the `DICOMs3Client`, i.e., allow a Python program to point it to any bucket that contains DICOM...

> Better to pre-index it since S3 is a shared resource and building the index is expensive. Ideally this architecture would be portable to other languages so an index that...