On 1/14/06, Paul Querna <[EMAIL PROTECTED]> wrote:
> Last week bloglines.com upgraded from 2.0.x to 2.2.x. At the same time,
> I switched us from mod_cgid to mod_cgi.
>
> mod_cgid has some problems if its path to the cgisock changes at any
> time, it really needs to call realpath() on the cgisock
Just in case other people want to jump in and fix things, here's a
list of stuff I think needs to be done in order to make httpd +
mod_proxy_fcgi a good replacement for the current popular fcgi
solutions (httpd 1.3.x and mod_fcgi and lighttpd + it's fcgi module).
Note that this is split up into th
Last week bloglines.com upgraded from 2.0.x to 2.2.x. At the same time,
I switched us from mod_cgid to mod_cgi.
mod_cgid has some problems if its path to the cgisock changes at any
time, it really needs to call realpath() on the cgisock path, to avoid
issues with how we distribute releases. (
Several quick comments Jorge,
first - the ASF only distributes binaries built by project members; that
doesn't prevent you or anyone of offering an independent binary build.
second - I *don't* forsee that we will backport all the compatibility of
Win64 to httpd 2.2. It's shaping up to be an evo
Joe Orton wrote:
The event MPM is listed in the "new features" document for 2.2, which
rather implies that it should work and is to some degree supported; yet
configure will issue the doom and gloom messages about the code being
incomplete and that nobody should use it except developers wishing
