Setting a preference clears the cache for that user already. This shouldn't be an problem.
CachingRecommender has nothing to do with diffs. There is no caching of diffs in that sense. 2011/2/24 Daniel Mühlbachler <[email protected]> > Nope, I tried that before and in my opinion the problem is the > CachingRecommender. I need a caching one because of the performance and > runtime. In fact, I must update or even clear the cache for the user who > updates his preferences. Information: I use a new CachingRecommender(new > SlopeOneRecommender(...), ...) > Additionally (I don't know if this matters), I use a MySQLDataModel but no > MySQLDiffStorage because it takes too long to build the diffs (after 3 hours > it even hadn't finished!). > So, all in all, if you say the SlopeOneRecommender does it itself, my > problem is the CachingRecommender that caches all diffs if they are called > once until the cache gets cleared. > >
