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

Allows non-inheriting trace context #470

Merged
merged 1 commit into from
Aug 18, 2017
Merged

Conversation

codefromthecrypt
Copy link
Member

@codefromthecrypt codefromthecrypt commented Aug 16, 2017

Eventhough convenience may mean an inheriting thread local is a good
choice, there are problems with this approach, such as the inability to
cleanup data. This encourages use of non-inheriting thread local w/o
changing the default.

fixes openzipkin-contrib/brave-opentracing#48

@codefromthecrypt
Copy link
Member Author

@gnoremac @schlosna do you think it is fair to recommend against using inheritable thread locals (leaving the default inheritable since we used to)?

Eventhough convenience may mean an inheriting thread local is a good
choice, there are problems with this approach, such as the inability to
cleanup data. This encourages use of non-inheriting thread local w/o
changing the default.
@codefromthecrypt
Copy link
Member Author

simplified the javadoc a bit, notably ridding the discussion about static references as the underlying problem is different tracer instances.

@codefromthecrypt codefromthecrypt merged commit f4310b8 into master Aug 18, 2017
@codefromthecrypt codefromthecrypt deleted the not-inheritable branch August 18, 2017 05:14
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

Successfully merging this pull request may close these issues.

Active span propagation issue
1 participant