[
https://issues.apache.org/jira/browse/SHIRO-796?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17226936#comment-17226936
]
Brian Demers commented on SHIRO-796:
------------------------------------
Shiro-Web does bind the Subject current thread (which would be a blocker for
you).
Taking a step back is there a specific environment/framework you are targeting?
I'm not saying this is a bad idea either, I'm just not sure what the
alternative is.
For async web apps, most frameworks have some way to hold context associated
with a request. You would need to stick the Subject in that context, and then
pull it out when needed.
> Move away from ThreadLocals
> ---------------------------
>
> Key: SHIRO-796
> URL: https://issues.apache.org/jira/browse/SHIRO-796
> Project: Shiro
> Issue Type: Improvement
> Affects Versions: 1.7.0
> Reporter: Boris Petrov
> Priority: Major
> Labels: loom, threadlocal
>
> Somewhat related to https://issues.apache.org/jira/browse/SHIRO-763.
> Shiro is using thread local variables a lot but they are generally
> frowned-upon and also the upcoming Project Loom could have problems with
> them. Projects are encouraged to move away from thread locals. It would be
> nice for Shiro to also do that.
> Some references:
> [https://channel9.msdn.com/Events/Java/JDConf-2020/Prepare-for-What-Looms-Ahead]
> [https://www.javaadvent.com/2019/12/project-loom.html]
> [https://cr.openjdk.java.net/~rpressler/loom/Loom-Proposal.html]
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
