|
From: McDonald, B. <Bru...@ba...> - 2003-12-15 14:31:10
|
Heres the email response to the email that I sent to Mike (foolishly not copying the list) -----Original Message----- From: Michael Ansley [mailto:mic...@ze...] Sent: Thursday, December 11, 2003 4:02 PM To: McDonald, Bruce Subject: RE: [Babeldoc-devel] Pipeline cache refreshing OK, so you are saying that generally, data config clients get their data on startup, and then wouldn't query for data again until a refresh took place (thus getting around the "change while processing" problem)? But, that behaviour is designed into each individual component, so it could be changed on a case-by-case basis? So, we could implement the Listener model, and then check each component to ensure that it's safe? Cheers... MikeA On Thu, 2003-12-11 at 20:37, McDonald, Bruce wrote: > Mike, > > You raise valid points, but I would caution you not to try to set policy globally. The pipeline (for instance) would know to reload its configuration only when no pipelines are running. This policy is pipeline specific. Other configuration data clients would be able to react differently to data change messages. > > Bruce. > > -----Original Message----- > From: Michael Ansley [mailto:mic...@ze...] > Sent: Thursday, December 11, 2003 1:40 PM > To: bab...@li... > Subject: RE: [Babeldoc-devel] Pipeline cache refreshing > > > I think that it requires more than that. First of all, do we want > pipelines changing while documents are being processed? If not, then, > do we version configs? How? What is the most basic operation that is > allowed a consistent set of config data? All pipelines should present a > consistent set of config data to any single document. Once any document > has started processing, the config data used for processing that > document should be fixed, in my opinion (I'm open to arguments to the > contrary, though). A guess it's a bit like transactioning metadata in a > relational database. If somebody does an ALTER TABLE that affects data > your query is busy with, you don't want it affecting your data (because > it's likely to be catastrophic). > > So, I'm open to ideas and opinions. > > Cheers... > > > MikeA > > > > On Thu, 2003-12-11 at 14:17, McDonald, Bruce wrote: > > Yes, > > > > Do that. > > > > At a more fundamental level, we probably need to implement an listener pattern on the configserver. The client classes of the configuration data (pipelines, journal, etc, etc) add themselves as data change listeners to the configuration classes thereby being notified when the underlying data changes. They could register for change notices when the config files changes... > > > > just an idea. > > > > Bruce. > > > > -----Original Message----- > > From: Michael Ansley [mailto:mic...@ze...] > > Sent: Wednesday, December 10, 2003 7:22 PM > > To: bab...@li... > > Subject: [Babeldoc-devel] Pipeline cache refreshing > > > > > > Hi, > > > > I'm back on the trail of config refreshing, and now attacking the > > pipeline configs. It seems that PipelineFactory has a method > > clearCache() and also clearCache(String name), but these methods are not > > deemed generic to the role of IPipelineFactory. Can I make them > > generic? Or are there implementations of IPipelineFactory for which > > they do not make sense? > > > > Cheers... > > > > > > MikeA > > > > > > > > > > > > ------------------------------------------------------- > > This SF.net email is sponsored by: SF.net Giveback Program. > > Does SourceForge.net help you be more productive? Does it > > help you create better code? SHARE THE LOVE, and help us help > > YOU! Click Here: http://sourceforge.net/donate/ > > _______________________________________________ > > Babeldoc-devel mailing list > > Bab...@li... > > https://lists.sourceforge.net/lists/listinfo/babeldoc-devel > > > > ------------------------------------------------------- > This SF.net email is sponsored by: SF.net Giveback Program. > Does SourceForge.net help you be more productive? Does it > help you create better code? SHARE THE LOVE, and help us help > YOU! Click Here: http://sourceforge.net/donate/ > _______________________________________________ > Babeldoc-devel mailing list > Bab...@li... > https://lists.sourceforge.net/lists/listinfo/babeldoc-devel |