Skip to content
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.

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

Define correct header to use for Correlation Context propagation #461

Closed
codeboten opened this issue Feb 13, 2020 · 2 comments
Closed

Define correct header to use for Correlation Context propagation #461

codeboten opened this issue Feb 13, 2020 · 2 comments

Comments

@codeboten
Copy link
Contributor

Adding this issue to track the recommendation from w3c discussed in w3c/baggage#16 on what the correct header name to use it.

Discussion originated here: #420 (comment)

@dyladan
Copy link
Member

dyladan commented Mar 3, 2020

Giving this a bump since now the Correlations API is in the spec and the wording in the current spec doc states that we are using the w3c editor's draft. I just want to state that I believe this is a dangerous idea as the spec is currently under heavy maintenance and things like the header name and/or the format of the value itself are likely to change. I think at the very least we should vendor-prefix our header name so we don't send/expect invalid headers when the spec is changed and finalized. A vendor prefixed name would also make an upgrade path very straightforward using the composite propagator.

@bogdandrutu
Copy link
Member

We went to use a different name and format for the moment.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants