--- steve [EMAIL PROTECTED] wrote:
I use it too, and have meddled with it enough at a source level to feel
comfortable running it. It has obvious, documented, problems (don't use
it with mod_ssl),
I didn't make it clear earlier -- I do use the event mpm.
Successfully. What *is* the
Ah, OK so I shouldn't panic until a browser ships with pipelining
enabled by default. HTTP pipelining would be nice, as in limited
tests, it had a nice performance increase on sites with lots of little
images/css/etc.
On 3/1/07, Greg Ames [EMAIL PROTECTED] wrote:
--- steve [EMAIL
On 2/27/07, Arnold Daniels [EMAIL PROTECTED] wrote:
Nick already told you, that Apache allows you to choose. So simply use
the fast-cgi/mpm-event combo, if you like that best. And if you want to
evangelize the combo, nobody is stopping you.
I use this and it works fine. However:
1. The event
steve wrote:
On 2/27/07, Arnold Daniels [EMAIL PROTECTED] wrote:
Nick already told you, that Apache allows you to choose. So simply use
the fast-cgi/mpm-event combo, if you like that best. And if you want to
evangelize the combo, nobody is stopping you.
I use this and it works fine.
On Wed, Feb 28, 2007 at 01:32:44PM -0800, Paul Querna wrote:
steve wrote:
On 2/27/07, Arnold Daniels [EMAIL PROTECTED] wrote:
Nick already told you, that Apache allows you to choose. So simply use
the fast-cgi/mpm-event combo, if you like that best. And if you want to
evangelize the
I use it too, and have meddled with it enough at a source level to feel
comfortable running it. It has obvious, documented, problems (don't use
it with mod_ssl),
I didn't make it clear earlier -- I do use the event mpm.
Successfully. What *is* the problem with mod_ssl anyway??? I have used
the
Hi,
1. Apache 2.2 can be used event based request handling, though is is
still under development. http://httpd.apache.org/docs/2.2/mod/event.html
2. Apache supports fast cgi
Best regards,
Arnold
howard chen wrote:
Can anyone give some comments abt in their implementations which are
Hello,
Thanks for your reply first.
I understand Apache already support fastcgi, however, phper most
likely will prefer mod_php, so fastcgi in Apache is not as popular as
in other http servers.
Similarly, later Apache 2.x might officially support event based model
rather than multi-process
On Tue, 27 Feb 2007 21:37:29 +0800
howard chen [EMAIL PROTECTED] wrote:
Hello,
Thanks for your reply first.
I understand Apache already support fastcgi, however, phper most
likely will prefer mod_php, so fastcgi in Apache is not as popular as
in other http servers.
You have the choice.
On 2/27/07, Nick Kew [EMAIL PROTECTED] wrote:
You have the choice. If more people use mod_php than fastcgi,
that's because they're choosing it.
yes, this is really interesting. sometimes i really don't understand them...
especially php does not recommended threaded MPM in apache2...so
Howerd,
PHP does not recommend running php as a module in a threaded
environment, because a number of PHP extensions are not thread-safe.
Apache2 MPM-prefork will run just fine with php as module.
Nick already told you, that Apache allows you to choose. So simply use
the fast-cgi/mpm-event
Since Apache 2.0, we've had the MPM architecture, which means you can
plug in your choice of processing model. That's also how Apache 2
works cross-platform, rather than being (like Apache 1) a Unix server
ported with lots of compromises in performance/etc to other platforms.
i was
On Tue, Feb 27, 2007 at 12:05:08AM +0800, howard chen wrote:
1. single-threaded, event-based, (powered by epoll)
httpd supports epoll() and event-based polling to the extent that the
system-call chains for handling a request by Apache httpd and lighttpd
are near-identical, it's hard to tell them
Can anyone give some comments abt in their implementations which are
difference from Httpd on the following area:
1. single-threaded, event-based, (powered by epoll)
2. fast cgi support
seems that these two points are quite attractive to use, why seldom
heard abt them in Httpd world?
:)
14 matches
Mail list logo
