Thanks for the feedback Jacob!
What you described makes sense - I've restored the original semantics and
broke
the "applications list" out into its own section.
The PR is updated if you'd like to give it another read. Hopefully its both
accurate to the original semantics and easier to read/understand :-)
- cpu
On Fri, Sep 23, 2016 at 6:30 PM, Jacob Hoffman-Andrews <j...@eff.org> wrote:
> On 09/21/2016 10:57 AM, Daniel McCarney wrote:
> > Section 6.1.2 ("Registration Objects") of the current draft[0] spends
> > 5 sentences describing the "applications" field of a registration
> > object. I think there was some drift here and parts still refer to
> > "authorizations" and the accompanying example object was incorrect
> > (providing 1 application URI instead of an array with the described
> > fields).
> The intent here was to have a single URL that would return a JSON list
> of application URLs. Because the list can get quite large, it could be
> broken into pages. It's relatively expensive to enumerate the whole list
> of pages in advance, and prone to errors when the list changes during
> iteration, so we only supported a notion of getting the first page, plus
> a "next" link. Here's an example (with very short pages):
>
> GET /acme/1234/applications
> 200 OK
> Link: href="/acme/1234/applications?cursor=888", rel="next"
> Content-Type: application/json
>
> [
> "https://example.com/acme/applications/4444";,
> "https://example.com/acme/applications/8888";
> ]
>
> GET /acme/1234/applications?cursor=8888
> 200 OK
> Link: href="/acme/1234/applications?cursor=9999", rel="next"
> Content-Type: application/json
>
> [
> "https://example.com/acme/applications/9000";,
> "https://example.com/acme/applications/9999";
> ]
>
> GET /acme/1234/applications?cursor=9999
> 200 OK
> Content-Type: application/json
>
> [
> "https://example.com/acme/applications/10000";
> ]
>
> I think breaking out the description of these "application list" objects
> into their own section makes sense, but I don't think the semantic
> changes in this PR are ideal.
>
>
_______________________________________________
Acme mailing list
Acme@ietf.org
https://www.ietf.org/mailman/listinfo/acme
