You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@jclouds.apache.org by "Adrian Cole (JIRA)" <ji...@apache.org> on 2014/10/05 22:48:33 UTC

[jira] [Commented] (JCLOUDS-153) Remove the jclouds Executors

    [ https://issues.apache.org/jira/browse/JCLOUDS-153?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14159695#comment-14159695 ] 

Adrian Cole commented on JCLOUDS-153:
-------------------------------------

Note that internally, we'll need to keep userExecutor for a wee bit as there's some scatter-gather code we haven't determined an alternate solution for. That said, we can certainly remove the io executor (for async http) and also the deprecated accessors.

> 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
>            Assignee: Adrian Cole
>
> 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)