> ++partNumber; > + BlobUploader b = > + new BlobUploader(mpu, partNumber, payload, parts); > + executor.execute(b); > + } > + executor.shutdown();
For a while we have talked about geting away from jclouds managing threads; we want the contexts to be more lightweight and default to caller context/single-thread execution. For performance-critical code like threaded multipart upload and clear container we can either take an explicit `ExecutorService` or push it into the `ContextBuilder`. The latter is more discoverable but feels more clunky, but in the end the user should manage the lifetime. --- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/jclouds/jclouds/pull/975/files/70ba6e0f5aa5c660cab27eb6a450ca7f1e435235#r67949555
