> +
> + /**
> + * List the snapshots in a given @{link Location}.
> + *
> + * @param locationId The location to search in.
> + * @return the set of @{link Snapshot}s we have access to in the given
> @{link Location}.
> + */
> + Set<Snapshot> listSnapshotsInLocation(String locationId);
> +
> + /**
> + * List the snapshots associated with a given volume.
> + *
> + * @param id The id of the volume to look at.
> + * @return the set of @{link Snapshot}s associated with this volume, if
> any.
> + */
> + Set<Snapshot> listSnapshotsForVolume(String id);
Well, we use set when set adds value. i recall a discussion w tperiels
about this some time back.
On Thu, Sep 19, 2013 at 8:10 PM, Andrew Bayer <[email protected]>wrote:
> In
> compute/src/main/java/org/jclouds/compute/extensions/VolumeExtension.java:
>
> > +
> > + /**
> > + * List the snapshots in a given @{link Location}.
> > + *
> > + * @param locationId The location to search in.
> > + * @return the set of @{link Snapshot}s we have access to in the given
> > @{link Location}.
> > + */
> > + Set<Snapshot> listSnapshotsInLocation(String locationId);
> > +
> > + /**
> > + * List the snapshots associated with a given volume.
> > + *
> > + * @param id The id of the volume to look at.
> > + * @return the set of @{link Snapshot}s associated with this volume, if
> > any.
> > + */
> > + Set<Snapshot> listSnapshotsForVolume(String id);
>
> Yeah, the approach I was gonna go for was to squash down to a flat Set in
> the Extension implementations. But I defer unto consensus on the right way
> to go.
>
> —
> Reply to this email directly or view it on
> GitHub<https://github.com/jclouds/jclouds/pull/109/files#r6468084>
> .
>
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds/pull/109/files#r6469078
