On Mon, 2008-09-29 at 18:40 -0400, Ryan McKinley wrote:
> On Sep 29, 2008, at 5:59 PM, Thorsten Scherler wrote:
>
> > On Mon, 2008-09-29 at 03:07 +0000, [EMAIL PROTECTED] wrote:
> > ...
> >> + <!-- Droids -->
> >> + <bean name="org.apache.droids.api.Droid/hello"
> >> + class="org.apache.droids.crawler.CrawlingDroid">
> >> + <constructor-arg ref="taskMaster" />
> >> + <constructor-arg ref="org.apache.droids.impl.SimpleTaskQueue" />
> >
> > Why did you renamed the droid?
> >
>
> I'm hoping that 'CrawlingDroid' becomes the standard crawling droid --
> useful off the shelf. Likewise the WalkingDroid would be a useful off
> the shelf file system walker.
Meaning they are the replacement for the abstract droids we had before.
>
> A HelloDroid example could perhaps extend CrawlingDroid and do
> something not generally useful -- just as an example of how it could
> be extended.
>
> does this make sense?
>
Yes, I agree.
>
> > I saw you removed the abstract droid/worker wouldn't make it sense to
> > have them?
> >
>
> Given that the TaskMaster actually handles all the common work, what
> would the AbstractDroid do? It could be there to hold on to the
> common things a Droid will do:
See above. I agree.
Cheers Ryan.
salu2
>
> private final TaskQueue queue;
> private final TaskMaster taskMaster;
>
> public AbstractDroid( TaskQueue queue, TaskMaster taskMaster )
> {
> this.queue = queue;
> this.taskMaster = taskMaster;
> }
>
> anything else?
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
--
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]
