Re: [Acme] Paging for authorizations and certificates lists

[Salz, Rich]

> 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
https://www.ietf.org/mailman/listinfo/acme

Re: [Acme] Paging for authorizations and certificates lists

[Salz, Rich]

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 mailing list
Acme@ietf.org
https://www.ietf.org/mailman/listinfo/acme

Re: [Acme] Paging for authorizations and certificates lists

[Martin Thomson]

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  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

Re: [Acme] Paging for authorizations and certificates lists

[Ted Hardie]

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 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.
>
>
So the current method is to return an array of strings within a JSON
object, where the strings are themselves URIs.  You anticipate that this
array will be large enough to require a separate response?  The overall
object limit is 128KB, right?  That's a lot of URIs.

Ted



> ___
> 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

[Acme] Paging for authorizations and certificates lists

[Jacob Hoffman-Andrews]

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