I agree that we could have a better marker, but I'm just going off the spec at the moment.
I've checked the agreed blueprint, and caching in zones is out of scope for Cactus. Please propose a discussion topic for the Design Summit. Justin On Wed, Mar 16, 2011 at 12:21 PM, Eric Day <[email protected]> wrote: > On Wed, Mar 16, 2011 at 06:47:03PM +0000, Ed Leafe wrote: > > > With our approach to pagination, without caching, the answer is always > correct: each query always returns the next {limit} values whose ID is >= > {start-id}. > > > > But for this example, you have to traverse *all* the zones in order > to get the list of instances for a customer. How else would you define > "instances 101-199 of 823 total instances"? How would you know where #101 > is? > > The marker should be the canonical zone:instance, so you just query > that zone with instance marker and limit, and move on to the next > zone(s) if your limit is not reached. You never need to build the > full list. > > -Eric >
_______________________________________________ Mailing list: https://launchpad.net/~openstack Post to : [email protected] Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
