"Brekke, Jeff" wrote:
> > See above. I'm interested in the Scheduler mechanism.
> > Currently, I'm implementing
> > Resources as "implements Runnable", so that they can be used
> > (casted) as
> > parameters for their own update tasks. I will look if it
> > would be simple to change
> > this so that they encapsulate a Turbine Scheduler job, instead.
>
> FYI: I've created a TurbineNonPersistentScheduler that will initialize the
> scheduler with jobs from the properties file and doesn't require a db
> backend to function. Shortly I'll present the changes on the Turbine list
> to see if there are any objections to committing it.
>
> My quick thoughts were to take the three daemons we have now: Feed,
> DiskCache, and BadURL, convert them to scheduled jobs using the above
> scheduler, dumping the daemon facility. Sounds like we'll need something
> different for what you and Raphael are proposing.
>
It looks interesting for the BadURL daemon. Bad URLs stop the thread for a lot of
time (when errors are related to DNS failures or the host is not answering), so it
makes sense to flag them and stop trying to use them. But there is a risk that a
transient network error marks lots (or all) of the resources as bad. The daemon, or
scheduled task, makes sense to check that resources are now available.
>
> -----------------------------------------------------------------------
>
> This message has been scanned for viruses with Trend Micro's Interscan VirusWall.
>
> --
> --------------------------------------------------------------
> Please read the FAQ! <http://java.apache.org/faq/>
> To subscribe: [EMAIL PROTECTED]
> To unsubscribe: [EMAIL PROTECTED]
> Archives and Other: <http://marc.theaimsgroup.com/?l=jetspeed>
> Problems?: [EMAIL PROTECTED]
--
--------------------------------------------------------------
Please read the FAQ! <http://java.apache.org/faq/>
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Archives and Other: <http://marc.theaimsgroup.com/?l=jetspeed>
Problems?: [EMAIL PROTECTED]
