Add support for binary mode using NATS headers

[bruth]

Fixes #975 #1006

Release Note

For users of NATS server 2.2 or above, the binary content mode is now available
which encodes required, optional, and extension event attributes in the message
header rather than encoded in the payload.

Reviewer Notes

• I removed the trailing period for the numerical sections, apologies if that was intended and I will add them back
• In terms of field and value encoding, NATS headers follow the HTTP spec. For the sections that talked about the names and values I copied the relevant sections from the HTTP protocol binding doc, however another option could be to link to them to remove the redundancy.

/cc @derekcollison @duglin

[bruth]

@ColinSullivan1 Totally missed seeing the discussion in #975. If you or your team has a draft in place already I can close this, otherwise happy for this to be a starting point for edits.

[duglin]

I think the version remains the same since we're still technically in the 1.0.3 cycle.

[bruth]

Reverted.

[duglin]

@bruth thanks! I don't know NATS but it looks pretty good (and thorough) to me. I think the href checker errors are real though.

[bruth]

@duglin Thanks for the quick review. I fixed the links.

[ColinSullivan1]

@bruth, much appreciated - thank you! We had this on our list of TODO items but didn't get to this yet. LGTM!

[bruth]

@ColinSullivan1 happy to help, thanks for the review!

[bruth]

@duglin No rush, but is there anything remaining to do to get this merged?

[duglin]

Nope - just need approval from the group. We normally approve PRs on the Thursday calls but we also allow for at least 3 days of review and this one just missed the deadline for this week's call. So unless something big shows up I expect it to be approved next Thursday. You can see it on the agenda here: https://docs.google.com/document/d/1OVF68rpuPK5shIHILK9JOqlZBbfe91RNzQ7u_P7YCDE/edit#

[bruth]

Great thanks!

On May 13, 2022, GitHub Notifications ***@***.***> wrote: Nope - just need approval from the group. We normally approve PRs on the Thursday calls but we also allow for at least 3 days of review and this one just missed the deadline for this week's call. So unless something big shows up I expect it to be approved next Thursday. You can see it on the agenda here: <https://docs.google.com/document/d/1OVF68rpuPK5shIHILK9JOqlZBbfe91RNzQ7u_P7YCDE/edit#>

— Reply to this email directly, view it on GitHub <#1016 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe- auth/AAD5YRQYPDSJBL6RWLCB3LDVJ2QDVANCNFSM5VUSAS6Q>. You are receiving this because you were mentioned.Message ID: ***@***.***>

[duglin]

@cloudevents/notify please review in prep for Thursday's call.

[duglin]

Approved on the 5/19 call
thanks @bruth

[bruth]

@duglin Great thanks!