This is not true. If you are in a servlet environment, the servlet container will use the recommender in multiple threads which means the app does not block while the recommender is refreshed.
During the refresh process a new DataModel is built and the reference to that is simply switched once it is fully loaded. --sebastian 2012/2/25 Lance Norskog <goks...@gmail.com>: > You have to use two recommender objects if you want to serve > recommendations while refreshing. I don't think any of the > recommenders have that as part of the api contract. > > On Fri, Feb 24, 2012 at 8:31 AM, Aleksei Udatšnõi <a.udac...@gmail.com> wrote: >> Hi, >> >> I am using an item-based recommender inside a servlet and would like >> to reload its data periodically (from db). Each reload takes up to 30 >> sec. >> >> Recommender object is Refreshable and thus can do periodic reloads by >> using refresh() function. My only concern is the impact of reload on >> the live servlet users. >> >> I wonder what happens with existing recommender.recommend() requests >> while the recommender is being reloaded? Does it still use the old >> data until reload is completely finished? >> >> Thanks >> Aleksei > > > > -- > Lance Norskog > goks...@gmail.com
