I already use code that does batch processing in the background (no browser window used) in any hosting environment. The question is would something like this be useful to the Drupal community; if yes how can one override Drupal's batch operations to use my processor.
If your wondering I use my async workers in Imageinfo Cache and Boost. Imageinfo Cache has a better implementation then the one in Boost. I was thinking this could be it's own project as I find being able to do background processing very useful. So if your looking at how it's done, Imageinfo Cache has a fairly clean implementation. The one in boost is multi process but it's not clean so I wouldn't use it as the base. Making this multi process isn't that hard to do.
Thoughts?
Comments
More developments
http://drupal.org/project/drupal_queue
http://drupal.org/node/988192#comment-3847954
2 sandboxes popped up
http://drupal.org/sandbox/danithaca/1094642
http://drupal.org/sandbox/gielfeldt/1099060
development plan?
Hi mikeytown2,
Do you have a plan to extract your async worker code into a separate module? I don't work to write duplicate code for the sandbox project at http://drupal.org/sandbox/danithaca/1094642. Let me know. Thanks.
2 sandboxes popped up
http://drupal.org/sandbox/damz/1163570
http://drupal.org/sandbox/xatoo/1161070
Background Batch
Hi mikeytown2
Don't know if you've already seen it, but there's a Background Batch module, which is part of Background Process. It does exactly this. Overrides the default batch API so that it runs in the background, meaning the progress indicator page is revisitable. It doesn't work for batch operations performed by update.php yet.