Re: How php works?
| From: | Roman Neuhauser | Date: | Wed, 13 Dec 2006 13:28:05 +0000 |
| Subject: | Re: How php works? | ||
| References: | 1 2 3 | Groups: | php.general |
| Request: | Send a blank email to php-general+get-245797@lists.php.net to get a copy of this message | ||
# maillist.kai@gmail.com / 2006-12-13 18:57:58 +0800:
> On 12/13/06, Roman Neuhauser <neuhauser@sigpipe.cz> wrote:
> ># maillist.kai@gmail.com / 2006-12-13 14:15:26 +0800:
> >> 3. Take linux apache for example, if compiled as a apache module,
> >> and using prefork threading model, for example, if I have 100
> >> process, is that means I have 100 copy of PHP library local data(I
> >> assume only one reentrant excutable image) in each process? compare
> >> to a worker model, like 10 process and 10 threads in each one
> >> process, should it make a difference that we only have 10 copy of
> >> PHP library local data ?
> >
> >Practical concerns make your question moot: even if the basic
> >distribution was all threadsafe, you're bound to hit a library that
> >uses strtok(3) or strerror(3), or static variables. How much of the
> >code you rely on is labelled by its authors as threadsafe?
>
>
> So it is not a good idea to use worker and php module at the same
> time, but if no threadsafe problem , maybe my thinking is right?
vvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvv
> Btw, I thought strerror in libc were thread-safe.
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
In a touch of genius, you summed up the whole thread-safety problem
so succintly, it puts an end to the whole thread.
--
How many Vietnam vets does it take to screw in a light bulb?
You don't know, man. You don't KNOW.
Cause you weren't THERE. http://bash.org/?255991