Eric S. Johansson wrote:
- There are lot of concurrency problems on PHP that can not be solved
easily. This is a base problem on the PHP side.
from my perspective there are lots of problems with PHP that cannot be
solved easily. ;-)
hehe.. :-) The problem is that PHP depends on lot of third party
libraries and some of them are not thread safe. So, even if the PHP
concurrency model were perfect, it might be still some problems.
- Believe me or not, the performance is better using FastCGI.
Currently we are working on the handler_fastcgi implementation; it is
not ready yet, but I hope it will be working soon. :-)
you might also want to take a look at scgi
http://www.mems-exchange.org/software/scgi/
seems to have a lot of the advantages of fast CGI but it's simpler.
Yeah, I know it. It isn't supported in the main stream just because
it doesn't seem to be very useful. I mean, at this moment, only a few
Python guys are supporting that approach.
Anyway, as you said, it is really easy to implement, so if it gets
more popular we can write it down quickly.
on the other hand, as is far more common, the complicated wins out over
the good. Therefore you need to support FastCGI as well.
I think so :-)
BTW, what is the advantage of compiling Cherokee+PHP into a single
binary?
faster response for both forking and threaded environments by virtue of
all the code being in the same execution space. You don't need to
transfer data over a network interface. There's no worries about
authentication between WebServer and application server.
on the other hand, it's far easier to compromise a Web server when you
have merged both environments. Given that PHP has a history of being
the sendmail of the web set, this is a big concern.
did I forget anything?
That is only performance. The problem of that scheme is that it might
be a potential DOS for the web server. Just imagine a PHP method which
calls a blocking function from some native library, it will block the
whole server thread. With a few of those requests, you could have a
perfect DOS attack.
We have to make it secure. Then, we can start to speed it up. :-)
--
Greetings, alo.
_______________________________________________
Cherokee mailing list
[email protected]
http://www.alobbs.com/cgi-bin/mailman/listinfo/cherokee
