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
>
>
--
PHP Development Mailing List <http://www.php.net/>
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
To contact the list administrators, e-mail: [EMAIL PROTECTED]
