> * @return The details of all existing nodes. > */ > Iterable<? extends Node> listNodes(); > > /** > + * Lists the details of all existing nodes, executing concurrently using > the executorService. > + * > + * @return The details of all existing nodes. > + */ > + Iterable<? extends Node> listNodesConcurrently(ExecutorService > executorService);
I know I'm late to the party here and @nacx has already had a look at this, but these seems like a way to approach this issue which is quite different from the way things are managed elsewhere in jclouds? There, from what I can see, this kind of "additional retrieval info" (e.g. paging) is managed via an options object, which in this case would probably need to allow the user to pass in the executor service if we're not going to construct that inside jclouds. So we would get something like: ``` Iterable<? extends Node> listNodes(ListOptions options); ``` where one of the things you could supply for ListOptions would be `ListOptions.builder().concurrently(myExecutor).build()` or so..? --- Reply to this email directly or view it on GitHub: https://github.com/jclouds/jclouds-chef/pull/47/files#r15115179
