Thanks Les. I'll try to implement this in the next few days. Once i get it working, i can post my code in case anyone else is interested in this type of cache behavior.
On Mon, Oct 3, 2011 at 10:25 AM, dan [via Shiro User] < [email protected]> wrote: > I have seen this scenario of many gets from the cache. In our case, our > cache manager was Hazelcast, which means that with every get there is, at > the very least, a deserialization that occurs. I concur with Jiggy that one > get at the beginning of a web request should be sufficient. The approach > that this "caching" is in the realm of a caching manager is certainly > reasonable, but this seems to be a different sort of caching - call it > local, request-specific caching. > > Best, > Dan > > ------------------------------ > If you reply to this email, your message will be added to the discussion > below: > > http://shiro-user.582556.n2.nabble.com/Cache-called-too-many-times-per-request-tp6851915p6855818.html > To unsubscribe from Cache called too many times per request, click > here<http://shiro-user.582556.n2.nabble.com/template/NamlServlet.jtp?macro=unsubscribe_by_code&node=6851915&code=bWF0YW5AZW1hdGFuLmNvbXw2ODUxOTE1fDk2OTQ3MDg2Mg==>. > > -- View this message in context: http://shiro-user.582556.n2.nabble.com/Cache-called-too-many-times-per-request-tp6851915p6856400.html Sent from the Shiro User mailing list archive at Nabble.com.
