Hi Nikola,
You should be able to configure this by providing a custom Guice
module when creating the context, and binding there the
AsyncMultipartUploadStrategy interfaces to your custom
implementations. Something like:
Module uploadModule = new AbstractModule() {
@Override
protected void configure() {
bind(AsyncMultipartUploadStrategy.class).to(YourImplementation.Class);
// Bind S3/Swift strategy too
}
};
ContextBuilder.newBuilder(provider)
.modules(ImmutableSet.<Module> of(uploadModule))
(...)
.build();
On 23 July 2013 15:33, Nikola Knezevic <laladelausa...@gmail.com> wrote:
> Hi guys,
>
> I would like to implement my own multipart upload strategy, to be used
> instead of ParallelMultipartUploadStrategy in s3 and swift apis.
> However, I'm struggling to discover how to make all s3 and swift based
> APIs use the new strategy instead of the old one. Any pointers are
> more than welcome! :)
>
> Thanks in advance,
> Nikola
