@shevchenator What is the difference between the `subscriptions` and the `groupedsubscriptions` resource? I mean, when would a user be interested in calling the second one? (perhaps we could just remove it).
A first approach that comes to my mind is to do something similar to what we do in jclouds-chef. The Chef API only returns the name and URI of the resources when requesting a list, and it is up to the user to fetch the entire details. For example, when [listing Clients](https://github.com/jclouds/jclouds-chef/blob/master/core/src/main/java/org/jclouds/chef/ChefApi.java#L282-L295) we are returning only the names, and have a [strategy](https://github.com/jclouds/jclouds-chef/blob/master/core/src/main/java/org/jclouds/chef/strategy/internal/ListClientsImpl.java) accessible from the [ChefService](https://github.com/jclouds/jclouds-chef/blob/master/core/src/main/java/org/jclouds/chef/ChefService.java#L158) that can be used to concurrently fetch the details of each Client. It is up to the user to get only the list of names or the entire details. --- Reply to this email directly or view it on GitHub: https://github.com/jclouds/jclouds-labs/pull/12#issuecomment-22475069
