Skip to content

docs: add possibility of additional message modes. #660

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
grant wants to merge 5 commits into from
Closed

docs: add possibility of additional message modes. #660

Changes from all commits
Commits
Show all changes
5 commits
Select commit Hold shift + click to select a range
72857ad
docs: add possibility of additional message modes.
grant Jul 2, 2020
7b7bdd5
Update spec.md
grant Jul 3, 2020
5a94858
Update spec.md
grant Jul 9, 2020
7d7f34d
update spec
grant Jul 9, 2020
be580ee
docs: english typo
grant Jul 9, 2020
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
5 changes: 5 additions & 0 deletions spec.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -136,6 +136,11 @@ a stand-alone event format and stored in the message body.
A "binary-mode message" is one where the event data is stored in the message
body, and event attributes are stored as part of message meta-data.

Regardless of which mode is used, protocol bindings MAY choose to provide
additional formatting and structure to the message body. For example, a
wrapper around the event might be used, or several events could be batched
together into a single message.

#### Protocol

Messages can be delivered through various industry standard protocol (e.g. HTTP,
Expand Down