It makes sense to have a single point were response pagination is made in API processing, rather than scattering pagination across Nova REST controllers; unfortunately if I am not really able to comment how feasible that would be in Nova's WSGI framework.
However, I'd just like to add that there is an approved guideline for API response pagination [1], and if would be good if all these effort follow the guideline. Salvatore [1] https://specs.openstack.org/openstack/api-wg/guidelines/pagination_filter_sort.html On 5 November 2015 at 03:09, Tony Breeds <t...@bakeyournoodle.com> wrote: > Hi All, > Around the middle of October a spec [1] was uploaded to add pagination > support to the os-hypervisors API. While I recognize the use case it > seemed > like adding another pagination implementation wasn't an awesome idea. > > Today I see 3 more requests to add pagination to APIs [2] > > Perhaps I'm over thinking it but should we do something more strategic > rather > than scattering "add pagination here". > > It looks to me like we have at least 3 parties interested in this. > > Yours Tony. > > [1] https://review.openstack.org/#/c/234038 > [2] > https://review.openstack.org/#/q/message:pagination+project:openstack/nova-specs+status:open,n,z > > __________________________________________________________________________ > OpenStack Development Mailing List (not for usage questions) > Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev > >
__________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
