Nice! Sounds good to me. My concerns about redundant methods were because in (all?) other providers we have only two methods, and the method that receives the options parameter (with the marker and pagination stuff) returns just the `IterableWithMarker`, which is kinda a normal one. That's why I initially saw the method as redundant.
There are actually the two options: keep the three methods, or make the method that receives the options return a single page, not a "magic iterable" (as other providers do). The latter, though, motivated the discussion in my PR about users having to know how to build/get the advancing function vs the premature optimization of a specialised list. The actual plan with the three methods (and removing the token parameter) LGTM. I'm just rambling on to give the context to understand my comments, that are based on what I found when thinking about this in the other PR :) Thx for taking this! --- Reply to this email directly or view it on GitHub: https://github.com/jclouds/jclouds-labs-google/pull/78#issuecomment-61727059
