I hope, for everyone's sake, that (assuming we accept this PR, which is a good idea in general) implementations will be setting limits quite low before triggering paging. Otherwise, we will have a feature that is surprising when developers first encounter it. If you set the limit to 1000 entries in the list, then you will find that very few people encounter the problem, but those that do will find their tools fail them.
You should recommend a limit that is a small number, like 10. That might appear often enough that developers get the message. On 1 March 2016 at 16:30, Jacob Hoffman-Andrews <j...@eff.org> wrote: > I posted this pull request: > https://github.com/ietf-wg-acme/acme/pull/86/files > > For some accounts, the list of authorizations or certificates will be > too large to reasonably return in a single request. This adds a notion > of paging: you get an initial list of resources, with a link rel=next > pointing at a URL for more, if there are more. > > _______________________________________________ > Acme mailing list > Acme@ietf.org > https://www.ietf.org/mailman/listinfo/acme _______________________________________________ Acme mailing list Acme@ietf.org https://www.ietf.org/mailman/listinfo/acme
