Scott Lawrence wrote: > On Mon, 2010-02-22 at 01:33 -0800, George Niculae wrote: >> This problem is due to configured acegi user cache that keeps user >> details in memory for 2 minutes (when step 4 is executed the user >> details are not fetched from the database but are retrieved from user >> cache). >> >> 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 > > Do we have reason to believe that there's a performance problem that the > cache is needed to solve? > > The phrase "might be useful" is a red flag in a requirement, especially > when it's being used to justify additional complexity. >
+1 Unless we have a good reason, let's disable it. We don't even cache hibernate queries right now, and AFAIK, that improve performance a lot more than this. Arjun _______________________________________________ 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/
