[
https://issues.apache.org/jira/browse/JCLOUDS-153?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14238626#comment-14238626
]
Ignasi Barrera commented on JCLOUDS-153:
----------------------------------------
The I/O executor has been removed, but the user executor is still used in many
providers to perform concurrent operations. Next steps should be to identify
those providers and refactor them to accept an executor provided by the user.
One possible approach to ease the migration would be to refactor the classes
that use the user executor in a way similar to what I did with this class in
the DigitalOcean provider, providing a factory that allows the class to be
injected, but also requiring users to provide the executor to be used for
concurrency:
https://github.com/jclouds/jclouds-labs/blob/master/digitalocean/src/main/java/org/jclouds/digitalocean/strategy/ListSshKeys.java
> Remove the jclouds Executors
> ----------------------------
>
> Key: JCLOUDS-153
> URL: https://issues.apache.org/jira/browse/JCLOUDS-153
> Project: jclouds
> Issue Type: Sub-task
> Components: jclouds-core
> Affects Versions: 1.7.0
> Reporter: Ignasi Barrera
>
> Once all providers and apis have been un-asynched, the jclouds executors (and
> all their related stuff such as the FutureIterables class) used to perform
> the asynchronous api calls should be removed.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
