Re: TSRM coverage question
| From: | lo-tek | Date: | Wed, 19 Sep 2001 17:27:00 +0000 |
| Subject: | Re: TSRM coverage question | ||
| References: | 1 2 3 | Groups: | php.dev |
| Request: | Send a blank email to php-dev+get-66228@lists.php.net to get a copy of this message | ||
My concern is really with the globals and not the functions, so if two
threads cant simultaneously step on the same copy of globals referenced by a
tsrm resource id, then that solves my problem.
you then pass to bar). So thread safety should *not* be affected.
>
> But AFAIK TSRM* do NOT force serialized execution of functions, they just
> make sure that each uses a different set of php-globals. So if bar( ) is
not
> thread-safe, the whole function still won't be thread safe, no matter
> whether you use TSRM. It simply depends on the bar( ) function.
>
> I don't know what the solution should be, of course it will be some kind
of
> locking, but I don't know what would be the best solution.
>
> --Jeroen
>
>