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

Allow "static" access to the current Reactor #12

Closed
skunkiferous opened this Issue Sep 21, 2013 · 2 comments

Comments

Projects
None yet
2 participants
@skunkiferous
Copy link
Collaborator

skunkiferous commented Sep 21, 2013

Sometimes, it happens that deep in user code, you need to get access to the context within which that code is executed, without having to pass that context all the way down from the top of the stack. This is usually done in Java using Thread-local instances. Since Reactors are our "lightweight threads", it makes most sense to give a static access to them. So we would be tracking the reactor in the PoolThread, to allow this to be implemented (set current reactor in thread, when switching of reactor, such that we can then get the current thread, cast it to PoolThread, and ask for the reactor).

@ghost ghost assigned skunkiferous Sep 21, 2013

@ghost ghost assigned laforge49 Oct 7, 2013

@laforge49

This comment has been minimized.

Copy link
Owner

laforge49 commented Oct 7, 2013

Currently planned for 0.3.5.

@laforge49

This comment has been minimized.

Copy link
Owner

laforge49 commented Oct 7, 2013

Done: 4888a0a

@laforge49 laforge49 closed this Oct 7, 2013

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment