On 10/4/07, Lee Fyock <[EMAIL PROTECTED]> wrote: > > So, my feature request is to be able to tag jobs with an identifier so > that I can request them by that identifier instead of by the job ID I > get when I schedule it, since I'm not stashing that away anywhere. > > Yes, I can stash the ID away, but this seems like something that would > be useful. Does anyone agree? :-) > > I'm undecided whether you can have multiple jobs with the same tag or > not, and if so, does the "give me the job with this tag" returns an > array, etc.
Hey, it's an interesting idea. But one day or the other, someone will end up asking for this "tag database" to be persisted and then the scheduler will slowly become something very fat... I exaggerate... In OpenWFEru (the workflow and BPM engine), the object that scheduled a task keeps the job id reference (to unschedule it at will). You might think of your job as resources linked to a scheduler trigger (via the job id). Right, this task resource is out of the scheduler, but well, the scheduler only cares about scheduling stuff... Somehow, it's an interesting idea... I would implement it "memory only", no persistence (like the whole scheduler), String tags. job_ids = scheduler.find_job_ids 'elephant' What do you think ? Best regards, -- John Mettraux -///- http://jmettraux.openwfe.org --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "OpenWFEru users" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/openwferu-users?hl=en -~----------~----~----~----~------~----~------~--~---
