Why is the header prefix of the Spring module and the Kafka module inconsistent
The Header prefix in the Spring module is ce-, but the prefix in the kafka module is ce_, so that the Spring module cannot consume the messages produced by the kafka module
The Kafka Protocol binding specification does state that attributes are prefixed with ce_ in binary mode.
Sounds like a potential bug in the Spring module...
@dsyer is this a bug?
Missing feature maybe.
Can you tackle it? :smile:
Yeah, sure. I was meaning to do a Kafka sample anyway.
Any further progress on this? It seems like it's not super straight-forward if it's desirable to only have ce_ for a kafka binder, and retain ce- for other binders.
That’s the way the protocol binding is species… Kafka uses ce_ whereas HTTP uses ce-
Jem...
On Aug 5, 2021, at 1:53 PM, Dustin @.***> wrote:
Any further progress on this? It seems like it's not super straight-forward if it's desirable to only have ce_ for a kafka binder, and retain ce- for other binders.
— You are receiving this because you commented. Reply to this email directly, view it on GitHub, or unsubscribe.
That’ll teach me to respond to on my iPhone and not spell check…
IPad originated
On Aug 5, 2021, at 4:41 PM, Jem Day @.***> wrote:
That’s the way the protocol binding is species… Kafka uses ce_ whereas HTTP uses ce-
Jem...
On Aug 5, 2021, at 1:53 PM, Dustin @.***> wrote:
Any further progress on this? It seems like it's not super straight-forward if it's desirable to only have ce_ for a kafka binder, and retain ce- for other binders.
— You are receiving this because you commented. Reply to this email directly, view it on GitHub, or unsubscribe.