You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@shiro.apache.org by "Benjamin Marwell (Jira)" <ji...@apache.org> on 2020/11/04 11:46:00 UTC

[jira] [Commented] (SHIRO-763) Make Shiro's ThreadLocal Storage configurable

    [ https://issues.apache.org/jira/browse/SHIRO-763?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17226004#comment-17226004 ] 

Benjamin Marwell commented on SHIRO-763:
----------------------------------------

+1. Atomic* classes should do. We wouldn't even need the volatile keyword then, as only the contents are updated, never the object reference itself.

> Make Shiro's ThreadLocal Storage configurable
> ---------------------------------------------
>
>                 Key: SHIRO-763
>                 URL: https://issues.apache.org/jira/browse/SHIRO-763
>             Project: Shiro
>          Issue Type: Improvement
>            Reporter: Brian Demers
>            Priority: Major
>             Fix For: 2.0.0
>
>
> Allow for different strategies of thread-local storage in ThreadContext. Currently `InheritableThreadLocalMap` is used.
> See: http://shiro-user.582556.n2.nabble.com/Inheritance-of-Security-Context-causes-problems-in-EJB-container-td7579859.html



--
This message was sent by Atlassian Jira
(v8.3.4#803005)