Dave Bryson wrote:
>
> I just updated the Scheduler Service.
>
> Here's what changed:
> * Now a true Service.
> * Has a JobEntry table for persisting jobs. (see MySQL_user_permissions.sql &
> jobentysql.sql)
> * Loads all jobs from the database on startup
> * Thread per task.
>
> What I'm still working on ( should happen over the next week ):
> * UI for CRUDing jobs. ( in the meantime you can add jobs directly to the DB and
> it'll load them ).
> * Documentation - I plan on updating the getting started document and add a
> small tutorial on using
> the scheduler.
>
> I ran the scheduler for about a 12 hour period with 3 jobs and all seemed to
> work fine. Please
> let me know if you have any problems.
<snip>
+1. It is funny that you jumped on this. I was about to as well :)
The only requirement I have is that is uses XML as its repository
instead of SQL. Maybe I will write a way to have Turbine run from all
XML instead of hitting the database. Should just be a matter of meeting
the interface.
I personally think that for a lot of sites (Slashdot) that SQL isn't
needed and will just end up being something that will break. XML on the
other hand is much easier to maintain and configure (IMO) and nothing
can really break because it is simple.
OK. As a side rant. This would be cool from at least a cutting
edge/geek standpoint. We should be able to define the database in
XMLSchema and then write XSLT stylesheets for Oracle, Postgres, MySql
etc and then when we modify the original XMLSchema all the database
schema should change to reflect this.
Kevin.
--
Kevin A Burton ([EMAIL PROTECTED])
http://relativity.yi.org
Message to SUN: "Please Open Source Java!"
"For evil to win is for good men to do nothing."
------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Problems?: [EMAIL PROTECTED]
