Closed (won't fix)
Project:
Scheduler
Version:
7.x-1.x-dev
Component:
Miscellaneous
Priority:
Normal
Category:
Feature request
Assigned:
Unassigned
Reporter:
Created:
20 Jan 2014 at 14:21 UTC
Updated:
5 Sep 2016 at 12:25 UTC
Jump to comment: Most recent
Comments
Comment #1
jonathan1055 commentedHi lahode
Thanks for your comments and your interest in Scheduler. Job Scheduler is quite new (only existed since 6.x, for a bit over three years, Sept 2010) whereas Scheduler has been here for more than ten years (it was started in 2003 on 4.x) before Job Scheduler API was even thought of. As far as I know there was no discussion at the time when Job Scheduler API was being written as to how best to integrate/re-use/merge the modules.
Maybe you would like to put together a proper case for making this change, and we could consider it for D8. I would very much doubt we'd make such a big change within the D7 version. But if you convince us to investigate it further we will. There would have to be a very good fit of functionality and clear benefits for users and developers, not just a 'I find quite messy having feeds + job scheduler + scheduler' comment ;-)
Jonathan
Comment #2
lahode commentedYou're right, my comment is silly :)
I looked the code of your module, and I thing 1/3 of it could just disappear, the most complex one.
A nice advantage too, is that job schedule can run process periodically, imagine a news that should appear every month for instance.
Finally, by simplifying your code, it should be easier to adapt your module not only for nodes, but entities, which is in Drupal 7 or 8 very interesting
For your information: http://www.computerminds.co.uk/drupal-code/easily-scheduling-periodic-ta... shows that with a few lines, you can do magic
A rough idea:
Have a nice day
Comment #3
jonathan1055 commentedComment #4
jonathan1055 commentedI think it is time this issue was closed.
Also see #8 in #915492-8: Support of Job Scheduler and Queue API for better scaling