On Fri, 2008-09-19 at 00:37 +0200, Thorsten Scherler wrote: > On Tue, 2008-09-16 at 13:34 -0400, Ryan McKinley wrote: > > I've been going through the droids API trying to limit global access. > > For an inability to explain all my thoughts, I put a functional sketch > > on: > > > > http://svn.apache.org/viewvc?view=rev&revision=695984 > > > > I'm not totally happy with the names, but its a start... > > > > Some of the big changes to note: > > > > * The task management stuff is pulled out of AbstractDroid and added > > to TaskMaster.java / MultiThreadedTaskMaster.java > > I like the clarity of the API and I especially like the taskMaster.
Our naming and my personal understanding of them regarding their interaction with the queue: Crawler - will open the task to extract more tasks and add them to the queue - normally happening in the parse phase in a walker. e.g. HelloCrawler Walker - will open the underlying storing structure of the current processed task (e.g. file/dirs in a file system) and extract new task from it. Normally happen in the run method of a walker. e.g. FileSystemWalker Racer - will not use not use tasks to interact with the queue at all. Instead of the above usecases the interaction with the queue only happens once in the droid (and not in a walker) at the beginning. e.g. FileRenamerRacer Do we need all three types? A walker could be converted to a racer by moving the queue logic to the init() method of the walker. What are the benefits of a walker over a racer and vice versa? Is it possible to create a walker/racer in http and other protocols? What is the generic way to do so (-> protocol api is trying to solve this problem but not yet really)? salu2 -- Thorsten Scherler thorsten.at.apache.org Open Source Java consulting, training and solutions --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
