Return-Path: Delivered-To: apmail-httpd-dev-archive@www.apache.org Received: (qmail 91879 invoked from network); 24 Nov 2009 16:09:15 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 24 Nov 2009 16:09:15 -0000 Received: (qmail 44362 invoked by uid 500); 24 Nov 2009 16:09:14 -0000 Delivered-To: apmail-httpd-dev-archive@httpd.apache.org Received: (qmail 44279 invoked by uid 500); 24 Nov 2009 16:09:14 -0000 Mailing-List: contact dev-help@httpd.apache.org; run by ezmlm Precedence: bulk Reply-To: dev@httpd.apache.org list-help: list-unsubscribe: List-Post: List-Id: Delivered-To: mailing list dev@httpd.apache.org Received: (qmail 44270 invoked by uid 99); 24 Nov 2009 16:09:14 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 24 Nov 2009 16:09:14 +0000 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of olafvdspek@gmail.com designates 209.85.210.189 as permitted sender) Received: from [209.85.210.189] (HELO mail-yx0-f189.google.com) (209.85.210.189) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 24 Nov 2009 16:09:06 +0000 Received: by yxe27 with SMTP id 27so6135579yxe.10 for ; Tue, 24 Nov 2009 08:08:45 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:content-type :content-transfer-encoding; bh=BpWFa5nvzBTg+weWjVC+KDVQyeqB9BbbIj6HG1mjLGk=; b=XgNpQR1MZDcalaG/YJbuMTUiwBWDEMNrLx0yOUaLdwcMb5Q/miZLqZ4XsE5vIaI46g YqXhshbIIiVS6t/PWaFX09Dq90Vz5lyTeSm5bBgODg5EnEugUjo68qRhcwKmO/pip+Py bH3m32SbdYnNQgW28h/EQiNIpdW2kO1Xqr9Pk= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type:content-transfer-encoding; b=fiDaGNhpXGhlfOBHunS5ZpGX+W5SAL5jhnZ4UVMF9VxST7CQ58HjsQ1g6198xBPHIv WEzRUuSS2shZ5N8j69/lICFYQ7cs7Js2U1Fg6vwGzlrODAG1Js3IgHQSaHPW1eKz8yXb AgzgLt0Bb9mppP8e0xSqXdlTn9boEqz7h1pCc= MIME-Version: 1.0 Received: by 10.150.246.10 with SMTP id t10mr11408762ybh.226.1259078922943; Tue, 24 Nov 2009 08:08:42 -0800 (PST) In-Reply-To: References: <1082520665@web.de> Date: Tue, 24 Nov 2009 17:08:42 +0100 Message-ID: Subject: Re: [mod_fcgid] Feedback / Suggestions From: Olaf van der Spek To: dev@httpd.apache.org Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Virus-Checked: Checked by ClamAV on apache.org On Tue, Nov 24, 2009 at 5:03 PM, Jeff Trawick 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? > > mod_fcgid is actually not bundled with the HTTP server. =C2=A0It is > released on its own cycle, and supports httpd 2.0.x, 2.2.x, and trunk > (future httpd 2.4.x) with one delivery. Ah, nice. What's the reason it's not bundled though? In this case, I'd love to see support for TCP/IP backends too. Shouldn't be too hard to implement. >> So what's the plan for 2.4? Have both of them? Or is mod_proxy_fcgi >> expected to be not ready for 2.4? > > mod_fcgid will support 2.4. =C2=A0proxy-fcgi folk(s), care to speak up on= your baby? Olaf