Closed (won't fix)
Project:
CLI Daemon
Version:
6.x-6.x-dev
Component:
Code
Priority:
Normal
Category:
Feature request
Assigned:
Reporter:
Created:
29 Mar 2011 at 13:21 UTC
Updated:
1 Jul 2014 at 17:18 UTC
Jump to comment: Most recent
Anyone started working on a D7 port?
Comments
Comment #1
pounardThis is indeed a really good idea an it is highly do-able.
I'm assigning this task to myself, I'll try to do either next weekend either one day the next week.
Don't hesitate to put new comments on this issue if you don't see activity so it'll get back on the top of my recent posts.
Comment #2
lee20 commentedSubscribing.. I could really use a D7 version of this module :)
Comment #3
pounardI'm starting working on it right now, don't promise you a release by tomorow, but I least I start working on it :)
Comment #4
pounardStarted new module Advanced Batch, actually in sandbox state. Daemon CLI won't have a Drupal 7 version but a direct port of this module will be provided in the Advanced Batch module, which provides a nice API for managing long time run tasks. D7 Daemon CLI will directly use it.
Setting this issue as postponned, I will post updates as soon as Advanced Batch reaches a usable state.
Comment #5
pounardFYI the Advanced Batch module as been greatly improved. The Daemon CLI is being fully rewritten, and now support multiple process spawning, with process watching, using a event based object oriented core, with a non active wait based algorithm.
The daemon now does nothing except running the cron because I need to figure out a nice API that would allow to control it easily without making it dependent of Advanced Batch, if I or anyone figure out something clean and easy to use/maintain enough I'll probably keep this module independent from Advanced Batch and let him leave here.
Any suggestion are welcome, you can see and test the code there (yes it works!). Please consider that right now, it really needs some tiny bits of the Advanced Batch module API arround (event handling interfaces) but they can be splitted out someway, it was just a matter of avoiding code duplication.
Comment #6
pounardClosing this, both the issue and module are way too old.