Hi,

We noticed that 3-4 years back jClouds had async implementations which was then 
deprecated and removed: https://issues.apache.org/jira/browse/JCLOUDS-40 

We were wondering why this decision to deprecate the Async implementation was 
made?

The reason I ask this question is that we are using a S3 proxy 
(https://github.com/andrewgaul/s3proxy) which internally uses jClouds. The 
problem is that the throughput is limited by the number of threads in the 
server to handle the request. We were planning to do changes to go to async for 
better performance and then we noticed your jira issue to remove async.

Regards,
Spandan Thakur

Reply via email to