--- On Tue, 2/23/10, Arjun Nair <[email protected]> wrote:
> >> I can see 2 ways to solve this: > >> - use a null user cache - that's it, no cache to > be kept > >> - register a dao listener that removes users from > cache when a user is deleted / saved > >> > >> Personally I vote for the 2nd one since the cache > might be useful > >> > >> Please share your thoughts, > >> > In terms of performance gains, I definitely agree the cache > is a good thing, but IMO, we are going to get a lot more > mileage by optimizing some of the HQL queries than caching > the auth tokens. > > So, in short I think we need to spend more time > investigating the cache, and I am not sure if it's worth > doing so in this release at least. Maybe we could disable > it, and look at it properly for the next release. What do > you think? > Agree, I've committed r18095- http://code.sipfoundry.org/changelog/sipXecs/?cs=18095 that replace the eh based user cache with null user cache (no cache). I've also raised http://track.sipfoundry.org/browse/XX-7732 to investigate cache usage / put it back in next release. George _______________________________________________ sipx-dev mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-dev Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-dev sipXecs IP PBX -- http://www.sipfoundry.org/
