Create a non-blocking API for the Fetcher class (or create an alternate class)

XMLWordPrintableJSON

    • Fully Compatible
    • v5.0
    • Sharding 2021-07-12, Sharding 2021-07-26, Sharding 2021-08-09
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      The Fetcher class only has a blocking way of waiting for outstanding requests to complete. This is a problem in cases where we need to use the Fetcher from inside a thread pool. We should either create an alternative Fetcher class (e.g. AsyncFetcher) that provides a non-blocking version of the same functionality, or refactor the AsyncFetcher to allow it to provide both blocking and non-blocking APIs, and probably implement the blocking ones in terms of the non-blocking ones.

            Assignee:
            Jason Zhang (Inactive)
            Reporter:
            Matthew Saltz (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            7 Start watching this issue

              Created:
              Updated:
              Resolved: