I recently created a job queue system at work for managing tasks that should be completed in the background. I'll be porting this over to fuel and was wondering if anyone else found this to be "core worthy" or should I make it a standalone package. You may use this functionality to schedule emails to be sent, update information via external api, or whatever else you may need to do that could bog down page load time.
The jobs would be run via a task that could be invoked by a cronjob or as a daemon. You would be able to specify a priority for the job so more important ones would be run before less important ones. You would also be able to schedule reoccuring jobs for things like updating a cache or sending out daily digest emails. The data for the jobs would be stored in either mysql or mongodb (when that class is available) via a driver system so you could extend it for something like rabbitmq.
So thats basically it. Let me know what you guys think and if you have any suggestions.
Donate
