Replies: 1 comment 1 reply
-
I believe the current configuration always uses the HTTP binary encoding (with CloudEvents as headers). I suspect there are efficiency reasons for doing so -- is there a particular reason for preferring one over the other in your use case? |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Hi,
I'm starting experimenting with Knative, and familiarize with Cloudevents.
I'm currently pushing events to the broker events using the Cloudevent Python SDK using the JSON format.
I connected a service through a trigger, but I was surprised to receive them as CloudEvents using HTTP binding protocol. Can we specify what format we want from the broker ? As I am in dev mode, i'm using the default In memory broker.
Thanks in advance :).
Beta Was this translation helpful? Give feedback.
All reactions