Right now, the status() method of RigettiQCSJob immediately blocks, waiting for results. To speed things along we should somehow make the polling/waiting for results asynchronous so that status() can return immediately and properly indicate whether the results are ready to fetch via result().
A couple options:
A threadpool (maybe in the backend, maybe with green threads) that jobs use to wait on their results.
A new QCS backend method for checking status which status() calls (either blocking or threaded periodically) rather than getting the results being the only way to get status.
Right now, the
status()method ofRigettiQCSJobimmediately blocks, waiting for results. To speed things along we should somehow make the polling/waiting for results asynchronous so thatstatus()can return immediately and properly indicate whether the results are ready to fetch viaresult().A couple options:
status()calls (either blocking or threaded periodically) rather than getting the results being the only way to get status.