... yeah, I had hoped to avoid the complexities that come from making this a full-fledged arbitrary dependency system and dealing with circularities and all that.
Perhaps to rationalize this particular situation, I can replace the part that auto-reloads every x minutes, with a mechanism that will reload on demand, but not more than every x minutes. I think that fits the model better actually, and should be more efficient. Or is it important to get updates more quickly -- how quickly? On Wed, Jan 28, 2009 at 7:08 PM, Otis Gospodnetic <[email protected]> wrote: > Would it be possible to create appropriate abstract methods in appropriate > classes (sorry for vagueness, I'm not yet familiar with the code enough to > suggest exact places) that would allow dependent classes to list for events > triggered/processed by classes they depend on. Here is a concrete example. > I like how the FDM re-checks the file and re-loads it. The Recommender > depends on data read by FDM. So I would hope I could add Recommender as a > FDM event listener. The FDM might have a method such as > addListener(FDMListener), abstract beforeReload(...) and abstract > afterReload(...). These methods would be called and implemented by > Recommender, which could then clear its cache or do nothing.
