Skip to content

Conversation

lance
Copy link
Member

@lance lance commented Jul 24, 2020

Note that I did not add a third Protocol parameter to Receiver.accept since
that would not currently be used. It's non-breaking to add a third parameter
in the future once additional protocols are supported.

Fixes: #266
Fixes: #261

BREAKING CHANGE

Note that I did not add a third `Protocol` parameter to `Receiver.accept` since
that would not currently be used. It's non-breaking to add a third parameter
in the future once additional protocols are supported.

Fixes: cloudevents#266
Fixes: cloudevents#261

BREAKING CHANGE

Signed-off-by: Lance Ball <lball@redhat.com>
@lance lance requested review from a team, danbev, grant, helio-frota and lholmquist and removed request for a team July 24, 2020 14:18
@lance lance added module/lib Related to the main source code module/transport/http Issues related to the HTTP transport protocol implementation type/enhancement New feature or request version/3.x Issues related to the 3.0 release of this library labels Jul 24, 2020
@lance lance mentioned this pull request Jul 24, 2020
@lholmquist lholmquist merged commit 9ae32c7 into cloudevents:master Jul 24, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
module/lib Related to the main source code module/transport/http Issues related to the HTTP transport protocol implementation type/enhancement New feature or request version/3.x Issues related to the 3.0 release of this library
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Remove Concept of Multiple Protocols within HTTP 1 line parse CloudEvent from HTTP Request
3 participants