> Is there anything else that needs to be done here? > > There is one feature that I am developing in jclouds that is made easier > because of this change. Let me know if there's anything I can do to help make > progress on this.
I do not think `LocalAsyncBlobStore` is the appropriate place to start de-asyncification of blobstore providers. These fake providers should mimic the real providers as they exist today, and not as they might exist in the future. We should be trying to make the fake providers *more* similar to real providers, e.g., #382. Perhaps you can start a thread on jclouds-dev discussing if and how to make progress on de-asyncification of blobstore? While the compute committers have made good progress on this task, it is not clear that this is the best fit for blobstore or that we have sufficient volunteers to complete this. Starting with the s3 or openstack-swift providers would give us much more experience on how this will work with a purely synchronous interface. I have not investigated this at all and have concerns about how operations such as `clearContainer`, cancellation, or long-lived operations like Glacier will work. Do you have a specific task that this pull request blocks? Perhaps we can address that in some other way? --- Reply to this email directly or view it on GitHub: https://github.com/jclouds/jclouds/pull/220#issuecomment-45560184
