> * @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);
> If we're going to remove the methods in the next release, is it worth the > change? Probably not. Then again, if we're planning to remove them anyway, is there a smarter thing we can do right now? But I'm fine to merge this and pick up the discussion later. Just a thought on naming: how about following the "options-like" style and creating overloaded methods with the executor services as the last param, e.g. `listEnvironments(String environmentName, ExecutorService executorService);`? That also makes the deprecation and removal look less "heavyweight" because we're only removing an overloaded version of a method. --- Reply to this email directly or view it on GitHub: https://github.com/jclouds/jclouds-chef/pull/47/files#r15116845
