> -----Original Message-----
> From: Raphael Luta [mailto:[EMAIL PROTECTED]]
> Sent: Tuesday, November 28, 2000 8:39 AM
> To: JetSpeed
> Subject: Re: RegistryManager service landed
>
>
> "Brekke, Jeff" wrote:
> >
> > > There's only 1 package to implement as a service before
> we can remove
> > > the JetspeedServlet: the daemon stuff.
> >
> > I've been looking into this. There was talk of converting
> these to turbine
> > scheduled jobs and using the turbine scheduler. This is
> great, but will
> > require a database backend to hold the scheduled jobs,
> which in turn means
> > Jetspeed could not run without a database. John Thorhauer
> has created a
> > turbine scheduler that initializes from a properties file.
> We could use his
> > scheduler and implement it in Jetspeed or I was thinking of
> attempting to
> > merge this with the Turbine scheduler ( if possible ) and
> contrib back into
> > Turbine.
> >
> > Converting the daemon implementations into scheduled jobs seems
> > straightforward. Any comments? Am I missing something?
> >
>
> +1 for using scheduled jobs.
>
> I think it would be best to leverage the URLManager service
> in the process.
> If we define an extended URLInfo record, by adding the fields:
>
> updateFrequency: the number of seconds between updates for this URL
> lastUpdate: timestamp of the last update
> urlType: (FEED|CONTENT|...)
> source: Vector of URL of the feed(s) in which this URL is described
>
> We can write a URLManagerScheduledJob (executed at frequency
> set in JR.p) to
> schedule a DiskCacheUpdateJob on any entry whithout a pending
> DiskCacheUpdateJob in the schedule list to refresh the
> content of this URL
> at lastUpdate+updateFrequency and update the status and
> lastUpdate records
> in the corresponding URLInfo.
>
> If the URL updated is modified and the urlType is FEED, execute a
> FeedUpdateJob which would unregister/register all the entries in the
> URLManager whose source contains the feed URL.
>
> This has many advantages over the current system but will require the
> URLManager URL records to be stored in a DB for rapidity of access.
I'm confused, and it may me my lack of understanding the URLManager. Would
there be a scheduled job ( record in db ) for every url in the URLManager? (
potential for thousands? ) or would there be one job to go through the list
or urls in the manager, check to see if it needs to be updated, etc. ?
------------------------------------------------------------------------
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]
