[
https://issues.apache.org/jira/browse/SHIRO-796?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17226249#comment-17226249
]
Brian Demers commented on SHIRO-796:
------------------------------------
[~boris-petrov] Do you have a suggstion as a replacement? Those articles hint
that Loom will have some sort of alternative api:
{quote}One is associating data with a thread context. Fibers will probably need
this capability, too
{quote}
I'm not sure there is anything we can do until then, and Loom is will years out.
*NOTE*: A Shrio based application can be written without using thread local
storage today, but your application would need to access the current Subject
through some other mechanism. This often comes up for async web apps.
> 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)
