steve roussey wrote:
> I know my name can be easily traced to a website I own that only gets
> about 10M pv/day but I also work as a consultant for another that gets
> an order of magnitude more. So perhaps you do get more then them and
> get 1B pv/day and your dad can beat up my dad. Ug. Strike th
We've made a start a long time ago, and we do our best to keep all of PHP
thread-safe. On paper it is. When a bug appears we fix it. Is it a risk to
run it... I think it is but I have seen people running it successfully on
IIS for a long time. (I still think that's a bad idea though).
Andi
At
On 8/9/05, steve roussey <[EMAIL PROTECTED]> wrote:
> > My stuff is far bigger and busier than yours
>
> My spewing of stuff...
I often write things to make me feel better and delete them before
hitting send. Sort of stream of consciousness that I edit before
sending. IRasmus, apologize for being
On Aug 9, 2005, at 3:12 PM, steve roussey wrote:
On 8/8/05, Rasmus Lerdorf <[EMAIL PROTECTED]> wrote:
3. Problems with thread-safety of modules
You missed the most serious one. Thread safety problems in random
libraries you link in and we have absolutely no control over those.
OK, I am
On 8/8/05, Rasmus Lerdorf <[EMAIL PROTECTED]> wrote:
> > 3. Problems with thread-safety of modules
>
> You missed the most serious one. Thread safety problems in random
> libraries you link in and we have absolutely no control over those.
OK, I am confused. I always thought (an assumption with n
Hi Ron,
On Tuesday 09 August 2005 19:09, Ron Korving wrote:
> Nonetheless, Rasmus, isn't it something to work on? Like Steve said, #1 and
> #2 can be accomplished, and that would at least be a good start. You are
> right about the libraries, but in time, even these may become thread safe
> (of cou
If we find thread safety problems in PHP we will fix them, of course.
It's not like we ignore them. Same goes for extensions, except for
those which are specifically designed to access libraries that show no
signs of ever becoming thread safe.
At the same time, you need to recognize that develope
Nonetheless, Rasmus, isn't it something to work on? Like Steve said, #1 and
#2 can be accomplished, and that would at least be a good start. You are
right about the libraries, but in time, even these may become thread safe
(of course, likely not by anyone from the PHP-community). Why is this
thread
I work at a company with a high volume web site (you know the drill:
LVS directors managing a farm of webservers (with php accelerators) to
a few database servers (MySQL if you want to know -- anyone happen to
have experience with Emic clustering for MySQL, btw? OK, back on
topic...)
PHP4 and Apac
steve roussey wrote:
> I have read and understand that there are a number of issues:
>
> 1. Problems with the Apache2 sapi
> 2. Problems with thread safety in the Zend Engine or PHP itself
> 3. Problems with thread-safety of modules
You missed the most serious one. Thread safety problems in rand
10 matches
Mail list logo
