Accepts instead of PSON

Henrik Lindberg (JIRA) Wed, 15 Mar 2017 11:26:15 -0700

Title: Message Title

PUP-3552

The format on the wire is one of json or msgpack (etc) - that is basically what a reader would need to know to be able to read it.
Naturally the reader must for most use cases know how the read data is organized - is this a "catalog" or a "report" and if so what is the version/representation of that. You may need to know that before reading the stream (you may be a reader that only understand an older version of say "catalog").

Following mime standard - there is no way to say "this is json + our thing" - it works the other way around - "this is our thing - it is in json".
Hence my suggestion of:

application/vnd.puppet.pcore+{json|msgpack|...}

that would establish that this is a format that vendor puppet has defined and named, and then (after the +) what the encoding is (json, etc).
Ultimately followed by additional mime arguments that defines things like UTF-8.

If we decide to not follow the rules of mime we can do what we want.

Sometimes - part of the format can be derived by context - i.e. "I am asking a particular endpoint for 'json'", the endpoint (URL) defines the rest (version, it is a catalog, etc). If we however want an actual mime type that defines this in a context free way, we would need the more elaborate description.

Add Comment

This message was sent by Atlassian JIRA

--
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [email protected].
To post to this group, send email to [email protected].
Visit this group at https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.

Jira (PUP-3552) Use application/json Content-Type/Accepts instead of PSON

Reply via email to