Date: 09/19/01
- Next message: Nael Mohammad: "[PHP-DEV] 4.0.6 BUG with GCC 3.0.1"
- Previous message: J Smith: "[PHP-DEV] My new extension SEGSIGVs"
- In reply to: Jeroen van Wolffelaar: "Re: [PHP-DEV] TSRM coverage question"
- Next in thread: World Wide Web Cie: "Re: [PHP-DEV] TSRM coverage question"
- Reply: World Wide Web Cie: "Re: [PHP-DEV] TSRM coverage question"
- Reply: World Wide Web Cie: "Re: [PHP-DEV] TSRM coverage question"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
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: php-dev-unsubscribe <email protected> For additional commands, e-mail: php-dev-help <email protected> To contact the list administrators, e-mail: php-list-admin <email protected>
- Next message: Nael Mohammad: "[PHP-DEV] 4.0.6 BUG with GCC 3.0.1"
- Previous message: J Smith: "[PHP-DEV] My new extension SEGSIGVs"
- In reply to: Jeroen van Wolffelaar: "Re: [PHP-DEV] TSRM coverage question"
- Next in thread: World Wide Web Cie: "Re: [PHP-DEV] TSRM coverage question"
- Reply: World Wide Web Cie: "Re: [PHP-DEV] TSRM coverage question"
- Reply: World Wide Web Cie: "Re: [PHP-DEV] TSRM coverage question"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

