[
https://issues.apache.org/jira/browse/SHIRO-317?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13606666#comment-13606666
]
Mark Spritzler commented on SHIRO-317:
--------------------------------------
I've refactored the code to use Shiro's ThreadContext object. I am going to
create another comment with the new code.
I will say that this works to a degree, but not completely. Each request still
causes a lot of calls to the cache and therefore going to the cache store a lot
more than really needed. It looks like Shiro's interactions with the Cache is
multi-threaded, and therefore it won't reduce this down to just one or two
calls, but still many calls.
Mark
> Read session from cache once per request
> ----------------------------------------
>
> Key: SHIRO-317
> URL: https://issues.apache.org/jira/browse/SHIRO-317
> Project: Shiro
> Issue Type: New Feature
> Affects Versions: 1.1.0, 1.2.0, 1.2.1
> Reporter: Luke Biddell
> Assignee: Les Hazlewood
> Priority: Minor
> Fix For: 1.3.0
>
>
> As per our discussion on the mailing thread, I've wired up my sessions to be
> stored in memcached (membase in the longer term). On a per request basis I'm
> seeing approximately 5 hits on my cache to retrieve the session. I would
> expect to see only one hit per threaded request, with the session stored as a
> thread local.
> For distributed caches this saves on network calls and for local caches it
> will save on potential lock contention.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
