I love the implementation of the tag which leads me to another question -- is there a way to receive job scheduling information from the job object?
For example, if I retrieve all jobs tagged as "backup" -- it would be useful to know the scheduling information for each "backup" job. One approach could be to save the scheduling information to a database, tied to a job_id. This would work fine for jobs which are scheduled at an interval, but for jobs which run once -- you would have to manage synchronization of job status with a separate store to have an up-to-date list of jobs and their scheduled times (as well as frequency). So after a job is run, you would have to update the separate datastore to no longer show that job in the future schedule. Fears aside in making the scheduler a bloated mess - what are people's thoughts? One more thing - what about allow users to read all tags for jobs. So if you retrieved all jobs with a tag of "sunday", you could also view the other tags on that same job (e.g. "backup" in the example"). This would allow you to do things like store comments or other pieces of information into the tags :-) --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
