I have a suggestion. So the apache worker MPM is not being maintained anymore,
so Apache should just use the worker feature that lighttpd has and tweak it so
it works with apache HTTP Server. Save alot of time and effort.
tim...@email.com wrote:
I have a suggestion. So the apache worker MPM is not being maintained
anymore, so Apache should just use the worker feature that lighttpd has
and tweak it so it works with apache HTTP Server. Save alot of time and
effort.
I'm not aware that support for worker has been
On Tue, Nov 24, 2009 at 5:53 AM, Graham Leggett minf...@sharp.fm wrote:
tim...@email.com wrote:
I have a suggestion. So the apache worker MPM is not being maintained
anymore, so Apache should just use the worker feature that lighttpd has
and tweak it so it works with apache HTTP Server. Save
On Mon, Nov 23, 2009 at 6:59 PM, Jeff Trawick traw...@gmail.com wrote:
On Mon, Nov 23, 2009 at 6:33 PM, William A. Rowe Jr.
wr...@rowe-clan.net wrote:
traw...@apache.org wrote:
Author: trawick
Date: Mon Nov 23 23:17:51 2009
New Revision: 883540
URL:
On Tue, Nov 24, 2009 at 9:54 AM, traw...@apache.org wrote:
Author: trawick
Date: Tue Nov 24 14:54:03 2009
New Revision: 883712
URL: http://svn.apache.org/viewvc?rev=883712view=rev
Log:
document the new Mutex directive, pulling in any existing special
considerations described in the
Hi dev,
I'd like to suggest to following changes / offer feedback for mod_fcgid:
(1)
mod_fcgid should be capable of specifying an external FCGI server.
Assume a scenario where the backend FCGI server (e.g. PHP with
php-fpm) runs for security considerations prespawned on a separate
machine with
On Tue, Nov 24, 2009 at 10:05 AM, Edgar Frank ef-li...@email.de wrote:
Hi dev,
I'd like to suggest to following changes / offer feedback for mod_fcgid:
my 2cents below
(1)
mod_fcgid should be capable of specifying an external FCGI server.
(2)
In conjunction with (1), mod_fcgid should be
On Tue, Nov 24, 2009 at 4:24 PM, Jeff Trawick traw...@gmail.com wrote:
(1)
mod_fcgid should be capable of specifying an external FCGI server.
(2)
In conjunction with (1), mod_fcgid should be able to select the backend
server based on request data.
I'd much rather see effort put into
As with mutex implementations, APR pollset implementations, or the
underlying OS support, are occasionally broken for some
configurations; the access to multiple implementations in APR 1.4.x
lends itself to allowing the user to specify a non-default pollset
implementation.
For example, the
On Tue, Nov 24, 2009 at 10:34 AM, Olaf van der Spek
olafvds...@gmail.com wrote:
On Tue, Nov 24, 2009 at 4:24 PM, Jeff Trawick traw...@gmail.com wrote:
(1)
mod_fcgid should be capable of specifying an external FCGI server.
(2)
In conjunction with (1), mod_fcgid should be able to select the
--
From: Jeff Trawick traw...@gmail.com
Sent: Tuesday, November 24, 2009 11:24 PM
To: dev@httpd.apache.org
Subject: Re: [mod_fcgid] Feedback / Suggestions
On Tue, Nov 24, 2009 at 10:05 AM, Edgar Frank ef-li...@email.de wrote:
Hi dev,
I'd like
On Tue, Nov 24, 2009 at 4:47 PM, Jeff Trawick traw...@gmail.com wrote:
What was the reason to import mod_fcgi again? Wasn't the ETA of
mod_proxy_fcgi too high?
mod_fcgid was imported because it was
* widely used
* not actively maintained
* httpd developers were willing to adopt it
I felt
On Tue, Nov 24, 2009 at 4:50 PM, pqf p...@mailtech.cn wrote:
In this case, one httpd thread(process) will have to bind to one FastCGI
process.
I don't think connect() to a local pipe/unix domain socket is the
bottle-neck, so let it be?
Doesn't it require an extra round trip? It's probably
On Tue, Nov 24, 2009 at 10:58 AM, Olaf van der Spek
olafvds...@gmail.com wrote:
On Tue, Nov 24, 2009 at 4:47 PM, Jeff Trawick traw...@gmail.com wrote:
What was the reason to import mod_fcgi again? Wasn't the ETA of
mod_proxy_fcgi too high?
mod_fcgid was imported because it was
* widely used
On Tue, Nov 24, 2009 at 10:50 AM, pqf p...@mailtech.cn wrote:
(3)
mod_fcgid currently buffers the complete input from the client
(occasionaly in a temp-file if the request is large) before it passes it
through to a FCGI backend. Could this be made configurable in a way like
On Tue, Nov 24, 2009 at 5:03 PM, Jeff Trawick traw...@gmail.com wrote:
What advantages does fcgid have over proxy_fcgi (except being ready)?
integrated, on-demand process management
How valuable is that?
In most cases a static number of backends seems fine.
mod_fcgid isn't in 2.2, right?
(1)
mod_fcgid should be capable of specifying an external FCGI server.
(2)
In conjunction with (1), mod_fcgid should be able to select the
backend server based on request data.
I'd much rather see effort put into mod_proxy_fcgi to support this use
case. I wish somebody, perhaps
Jeff Trawick wrote:
On Tue, Nov 24, 2009 at 9:54 AM, traw...@apache.org wrote:
Author: trawick
Date: Tue Nov 24 14:54:03 2009
New Revision: 883712
URL: http://svn.apache.org/viewvc?rev=883712view=rev
Log:
document the new Mutex directive, pulling in any existing special
considerations
On Tue, Nov 24, 2009 at 11:53 AM, William A. Rowe Jr.
wr...@rowe-clan.net wrote:
Jeff Trawick wrote:
On Tue, Nov 24, 2009 at 9:54 AM, traw...@apache.org wrote:
Author: trawick
Date: Tue Nov 24 14:54:03 2009
New Revision: 883712
URL: http://svn.apache.org/viewvc?rev=883712view=rev
Log:
Jeff Trawick wrote:
On Mon, Nov 23, 2009 at 6:17 PM, traw...@apache.org wrote:
Author: trawick
Date: Mon Nov 23 23:17:51 2009
New Revision: 883540
URL: http://svn.apache.org/viewvc?rev=883540view=rev
There will likely be other issues to discuss about this, but to start with:
* you need an
On Tue, Nov 24, 2009 at 12:46 PM, Gregg L. Smith li...@glewis.com wrote:
Jeff Trawick wrote:
On Mon, Nov 23, 2009 at 6:17 PM, traw...@apache.org wrote:
Author: trawick
Date: Mon Nov 23 23:17:51 2009
New Revision: 883540
URL: http://svn.apache.org/viewvc?rev=883540view=rev
There will
Jeff Trawick wrote:
What about an optional third argument to Mutex to indicate that the
pid should be omitted?
Mutex default sysvsem
Mutex ssl-cache file:/mnt/sesscachedir OmitPid
etc.
That seems sensible, but I'm left wondering how many different naming
conventions we can fit on one
Maybe I should add, build will fail on line util_mutex.c line 160
unless DEFAULT_REL_RUNTIMEDIR is defined, whether by also including
mpm_default.h or adding a define in util_mutex.c or
util_mutex.h.
E:\build\httpd-2.3.x-dev\server\util_mutex.c(159) : error C2065:
'DEFAULT_REL_RUNTIMEDIR' :
On Tue, Nov 24, 2009 at 2:24 PM, Gregg L. Smith li...@glewis.com wrote:
Maybe I should add, build will fail on line util_mutex.c line 160
unless DEFAULT_REL_RUNTIMEDIR is defined, whether by also including
mpm_default.h or adding a define in util_mutex.c or
util_mutex.h.
traw...@apache.org wrote:
--- httpd/httpd/trunk/include/util_mutex.h (original)
+++ httpd/httpd/trunk/include/util_mutex.h Tue Nov 24 19:06:16 2009
@@ -99,9 +99,9 @@
const char **mutexfile);
/* private function to process the Mutex directive */
On Tue, Nov 24, 2009 at 1:58 PM, William A. Rowe Jr.
wr...@rowe-clan.net wrote:
Jeff Trawick wrote:
What about an optional third argument to Mutex to indicate that the
pid should be omitted?
Mutex default sysvsem
Mutex ssl-cache file:/mnt/sesscachedir OmitPid
etc.
That seems sensible,
On Tue, Nov 24, 2009 at 2:50 PM, William A. Rowe Jr.
wr...@rowe-clan.net wrote:
traw...@apache.org wrote:
--- httpd/httpd/trunk/include/util_mutex.h (original)
+++ httpd/httpd/trunk/include/util_mutex.h Tue Nov 24 19:06:16 2009
@@ -99,9 +99,9 @@
const
Jeff Trawick wrote:
no, even I could understand
I fixed it by hardcoding logs when DEFAULT_REL_RUNTIMEDIR isn't defined.
This works for me at least.
(mpm_default.h won't be found on Unix without build changes, and we
want to minimize affinity with any particular MPM anyway.)
I find that
William A. Rowe Jr. wrote:
traw...@apache.org wrote:
--- httpd/httpd/trunk/include/util_mutex.h (original)
+++ httpd/httpd/trunk/include/util_mutex.h Tue Nov 24 19:06:16 2009
@@ -99,9 +99,9 @@
const char **mutexfile);
/* private function to process
Jeff Trawick wrote:
Many if not all other functions which handle directives and which are
not implemented in the same file as the directive declaration also
have the ap_ prefix, so I don't follow you on the public aspect.
s/public/meant to be exported/
But most of these other functions are
Nick Kew wrote:
Regarding r883540 itself, I've just taken a look at it.
It seems to enforce the same mutex type on all modules that
use a mutex. Can't see an obvious reason not to do that, but
it might merit discussion on-list. For example, maybe someone
has a good reason to use different
On Tue, Nov 24, 2009 at 3:12 PM, Gregg L. Smith li...@glewis.com wrote:
Jeff Trawick wrote:
(mpm_default.h won't be found on Unix without build changes, and we
want to minimize affinity with any particular MPM anyway.)
I find that odd since I see it in the mpm_default.h files under all the
On Tue, Nov 24, 2009 at 3:00 PM, Jeff Trawick traw...@gmail.com wrote:
On Tue, Nov 24, 2009 at 1:58 PM, William A. Rowe Jr.
wr...@rowe-clan.net wrote:
Jeff Trawick wrote:
What about an optional third argument to Mutex to indicate that the
pid should be omitted?
Mutex default sysvsem
Mutex
33 matches
Mail list logo
