Re: [Acme] Paging for authorizations and certificates lists

> For arrays, yes. It follows the pattern established with Atom, but it's > fairly > widely used. You put N things in the response, then provide a rel=next link > for the next part. Thanks. ___ Acme mailing list Acme@ietf.org

Re: [Acme] Paging for authorizations and certificates lists

Are there common and well-specified semantics for merging "paged" JSON objects? Is his necessary? The serve can just stream it out and any client who is asking for this huge name must be willing to generate it, too. Or is that wrong? ___ Acme

Re: [Acme] Paging for authorizations and certificates lists

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

Re: [Acme] Paging for authorizations and certificates lists

On Mon, Feb 29, 2016 at 9:30 PM, Jacob Hoffman-Andrews 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

[Acme] Paging for authorizations and certificates lists

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