You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Refactor the current implementation to pull forking and in-process (no-fork) execution strategies into separate classes, which the worker processes will then use to actually spawn jobs according to sysadmin configuration. Then, add support for a FastCGI strategy, in addition to the forking and in-process strategies currently supported.
Current Behavior
Currently, only forking and in-process (non-forking) strategies are supported, and forking is used if it is supported, regardless of sysadmin preferences. This feature would allow the addition of other mechanisms under the hood, and give control over which to use to the sysadmin.
This feature was originally suggested and Pull Requested under the old home for this project. This issue is intended to pull this functionality over to the current repository.
The text was updated successfully, but these errors were encountered:
Expected Behavior
Refactor the current implementation to pull forking and in-process (no-fork) execution strategies into separate classes, which the worker processes will then use to actually spawn jobs according to sysadmin configuration. Then, add support for a FastCGI strategy, in addition to the forking and in-process strategies currently supported.
Current Behavior
Currently, only forking and in-process (non-forking) strategies are supported, and forking is used if it is supported, regardless of sysadmin preferences. This feature would allow the addition of other mechanisms under the hood, and give control over which to use to the sysadmin.
Possible Solution
The original attempt at this, by @ebernhardson, was in chrisboulton/php-resque#81
Context
This feature was originally suggested and Pull Requested under the old home for this project. This issue is intended to pull this functionality over to the current repository.
The text was updated successfully, but these errors were encountered: