<html><body>
<p><font size="2" face="sans-serif">First, here is some background on this topic: <a href="http://www.gossamer-threads.com/lists/openstack/dev/2777">http://www.gossamer-threads.com/lists/openstack/dev/2777</a></font><br>
<br>
<font size="2" face="sans-serif">Does anyone have any insight as to why offset is not supported in the REST API calls that support pagination? </font><font size="2" face="sans-serif"><i> </i></font><font size="2" face="sans-serif">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.</font><br>
<br>
<font size="2" face="sans-serif">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.</font><br>
<br>
<font size="2" face="sans-serif">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? <a href="https://github.com/openstack/cinder/blob/master/cinder/api/v2/volumes.py#L214">https://github.com/openstack/cinder/blob/master/cinder/api/v2/volumes.py#L214</a></font><br>
<br>
<font size="2" face="sans-serif">Thanks for the information.</font><br>
<br>
<font size="2" face="sans-serif">Steven Kaufer</font></body></html>