[MTOS-dev] TheSchwartz vs MT::TaskMgr

[Jay Allen]

Mark, that's super helpful information.  Thank you.  I didn't realize
even having read over the POD last night for TheSchwartz, that it
didn't do recurring jobs.

Frankly, given what I've seen in my investigation and what I've just
learned now, it seems like it would make the most sense to have a
beefed up MT::TaskMgr run as a a high-level management layer on top of
TheSchwartz (for viewing, re-prioritization and manipulation of tasks
in the UI) and then consolidate MT::Task and TheSchwartz to marry
reliability/power with recurring tasks.  Of course, I could be
completely off base here but at least from a developers standpoint,
I'd like to work with *just one* API.

I'd love to hear any other comments on the matter if you have thoughts.

-- 
Jay Allen
Endevver Consulting
415-200-6985

On Wed, Apr 2, 2008 at 8:38 AM, Mark Paschal <mark at sixapart.com> wrote:
> Jay Allen wrote:
>  > Oh wait, I see, you're saying the opposite! That is MT::TaskMgr is
>  > still being used for small periodic tasks while, on the other hand,
>  > the bigger jobs like republishing moved over to TheSchwartz.  Do you
>  > know if it's expected to remain like that or alternately whether there
>  > is any plan to migrate the remaining tasks over to TheSchwartz and
>  > either do away with MT::Task/MT::TaskMgr or to merge them with
>  > MT::TheSchwartz?
>
>  TheSchwartz is designed for one-time tasks, in that it doesn't provide
>  a way for jobs to recur. We could simulate it by always replacing
>  recurring jobs with the next scheduled run, instead of "finishing"
>  them as with one-time jobs, but it still sounds fragile. Code that
>  unintentionally marks a recurring job as completed or a database fault
>  of some kind could derail a job *and* its future occurrences.
>
>  OTOH, it would be nice to use TheSchwartz exclusively to do work.
>
>  If we did use TheSchwartz for scheduled tasks, we would probably have:
>
>  * a Schwartz job that performs generic MT::Tasks, and
>  * an MT::TaskMgr that still has the scheduling logic, but queues
>    Schwartz jobs instead of performing MT::Tasks directly.
>
>  I expect we'd keep the existing APIs for defining scheduled tasks,
>  even if we use TheSchwartz to do them.
>
>  We have not scheduled any work (heh) in this area, afaik.
>
>
>  Mark Paschal
>  Software developer, Movable Type
>  mark at sixapart.com
>  _______________________________________________
>  MTOS-dev mailing list
>  MTOS-dev at sixapart.com
>  http://www.sixapart.com/mailman/listinfo/mtos-dev
>