Re: Experiments with a threading library for Zend: spawning a new executor
| From: | Stas Malyshev | Date: | Wed, 19 Jan 2011 05:00:26 +0000 |
| Subject: | Re: Experiments with a threading library for Zend: spawning a new executor | ||
| References: | 1 2 3 4 5 | Groups: | php.internals |
| Request: | Send a blank email to internals+get-51311@lists.php.net to get a copy of this message | ||
Hi!
like "map" express this well. The idea is that the executor can start up with no variables in scope, though hopefully shared code segments,For that you would probably need to put some severe restrictions on your code, such as: 1. No usage of default properties or statics in classes or functions. 2. No assigning of constants to any variable (comparison and operators may be ok, not sure how refcounts work out) 3. No defining new functions or classes or including new files This probably could still do something useful - such as run 3 sql queries in parallel and return the result - but I'm not sure how you could enforce such conditions... If you do not, you'll have some "interesting" race conditions leading to variables disappearing, leaking, being assigned wrong values, etc. -- Stanislav Malyshev, Software Architect SugarCRM: http://www.sugarcrm.com/ (408)454-6900 ext. 227