[almighty] Pagination & jsonapi.org

[Konrad Kleine]

Hi Thomas,

here are my thoughts on this topic.

I understand that it isn't nice to parse the header values in HTTP
responses for pages. But I think it is the way everybody does it. (Doesn't
mean, we have to obey to this.)

The docker registry for example has a similar approach when browsing the
docker repositories: https://docs.docker.com/registry/spec/api/#/pagination

The downside is that you cannot jump to the page you want immediately
unless you do some calculation.

The number of pages in a live system can change while you're browsing
through the work items, because others might add or remove work items. This
should be considered when calculating the amount of pages.

Konrad


On Tue, Oct 4, 2016 at 8:26 AM, Michael Kleinhenz <kleinhenz at redhat.com>
wrote:

> >> The client then must compute how many pages there are and the size of
> the
> >> pages by parsing the uri's.
> >
> > Do we have a requirement for knowing the exact number of pages ?
>
> Only if UX decides for "paging" view instead of scrolling with
> lazy-loading. But even then, should not be a problem.
>
> -- Michael
>
> --
> Michael Kleinhenz
> Principal Software Engineer
>
> Red Hat Deutschland GmbH
> Werner-von-Siemens-Ring 14
> 85630 Grasbrunn
> Germany
>
> RED HAT | TRIED. TESTED. TRUSTED.
> Red Hat GmbH, www.de.redhat.com,
> Registered seat: Grasbrunn, Commercial register: Amtsgericht München,
> HRB 153243,
> Managing Directors: Paul Argiry, Charles Cachera, Michael Cunningham,
> Michael O'Neill
>
> _______________________________________________
> almighty-public mailing list
> almighty-public at redhat.com
> https://www.redhat.com/mailman/listinfo/almighty-public
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://listman.redhat.com/archives/almighty-public/attachments/20161004/28674348/attachment.htm>