First, here is some background on this topic: http://www.gossamer-threads.com/lists/openstack/dev/2777 Does anyone have any insight as to why offset is not supported in the REST API calls that support pagination? I realize that there are tradeoffs when using a offset (vs. marker) but I believe that there is value in supporting both. For example, if you want to jump to the n-th page of data without having to traverse all of the previous pages. Is there a reason why the APIs do not support either a marker or an offset (obviously not both) on the API request? It appears that sqlalchemy has offset support. Also, it seems that cinder at least looks for the offset parameter (but ignores it). Does this mean that it was supported at one time but later the support was removed? https://github.com/openstack/cinder/blob/master/cinder/api/v2/volumes.py#L214 Thanks for the information. Steven Kaufer -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20140318/f8505aeb/attachment.html>