[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Comments on the diagram (was: RE: [Pyatcron-devel-list] Cron backend: a
From: |
Julien Olivier |
Subject: |
Comments on the diagram (was: RE: [Pyatcron-devel-list] Cron backend: a correction) |
Date: |
Mon, 17 Nov 2003 11:19:31 +0000 |
Hi Xavier
I'd like to comment your diagram:
1) why do you split ScheduleedTask and GenericTask ? Isn't there 1 (1,1)
relation between them ? From what I see in your diagram, you seem to
want a (1,*) relation between. If I agree with it, doesn't it mean that
the ScheduledTask class should have a task _array_ property, as well as
appendTask(task), prependTask(task), removeTaskById(Id) and
getTaskById(Id) or something like that ?
2) In the ScheduledTask, I think that it should be arrays of minutes,
hours, days etc... as you can specify several dates for the same task.
3) I think the GenericTask should have functions like addParameter and
deleteParameter. It should automatically generate the execCommand from
it's sub-class properties. For example, an Archiver class, sub-class of
GenericTask would have a "archiverCommand" property as well as a
"pathToBackup" property. Now, calling the getExecCommand would generate
the "tar cvfz /tmp/pyatcrontmp645.tgz /home/pollux/important" command
using those properties.
I think that's all :)
BTW: thanks for your work. The diagram is a good idea, as well as the
docs in CVS.
--
Julien Olivier <address@hidden>
- RE: [Pyatcron-devel-list] Cron backend: a correction, (continued)
RE: [Pyatcron-devel-list] Cron backend: a correction, Childers, Matthew, 2003/11/13
RE: [Pyatcron-devel-list] Cron backend: a correction, Childers, Matthew, 2003/11/13
RE: [Pyatcron-devel-list] Cron backend: a correction, Childers, Matthew, 2003/11/13
RE: [Pyatcron-devel-list] Cron backend: a correction, Childers, Matthew, 2003/11/14
RE: [Pyatcron-devel-list] Cron backend: a correction, NICOLOVICI Xavier, 2003/11/17