[
https://issues.apache.org/jira/browse/SHIRO-317?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13609274#comment-13609274
]
Mark Spritzler commented on SHIRO-317:
--------------------------------------
Yeah, that last implementation works really well. In my testing the first time
someone logs in, I get two calls to the cache. 1 to check to see if there is
already an entry, and 2) if no entry add it to the back end cache.
On subsequent calls within that one request there are no more calls to the back
end cache, it just reuses the one in the ConcurrentHashMap.
On other requests later it gets it from the concurrent map.
Now, the only question left will be to incorporate the Invalidating Sessions.
For obvious reasons.
Thanks
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
