You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
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)
The text was updated successfully, but these errors were encountered: