Return-Path: Delivered-To: apmail-httpd-users-archive@www.apache.org Received: (qmail 61001 invoked from network); 12 Feb 2009 15:30:22 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 12 Feb 2009 15:30:22 -0000 Received: (qmail 67159 invoked by uid 500); 12 Feb 2009 15:30:10 -0000 Delivered-To: apmail-httpd-users-archive@httpd.apache.org Received: (qmail 66994 invoked by uid 500); 12 Feb 2009 15:30:09 -0000 Mailing-List: contact users-help@httpd.apache.org; run by ezmlm Precedence: bulk Reply-To: users@httpd.apache.org list-help: list-unsubscribe: List-Post: List-Id: Delivered-To: mailing list users@httpd.apache.org Received: (qmail 66985 invoked by uid 99); 12 Feb 2009 15:30:09 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 12 Feb 2009 07:30:09 -0800 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of covener@gmail.com designates 74.125.46.153 as permitted sender) Received: from [74.125.46.153] (HELO yw-out-1718.google.com) (74.125.46.153) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 12 Feb 2009 15:30:03 +0000 Received: by yw-out-1718.google.com with SMTP id 5so423177ywr.84 for ; Thu, 12 Feb 2009 07:29:42 -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=wy1ri9uXHq0f0cZaRJZkufzbFZ0tAKUts9w8BTG+J4Q=; b=IT1qIKYVmUh5AZFrl7YTvVcGzVQk/duLsE2mwypkGm+601u7gJCSnCteHgisoVniMk uLVAY7nA1f0icnOakwtm+c7PzbSjxMEjJIenIz/s7E+HCH7tDCOCSjXE2dnfkAeDB3YN 9PDYf9XCh0BnOHMOJlq3Xl0hW1cf3L+856NmQ= 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=uwOMFZjGHb/XNiyNrLQj4MSdyJ51745vJDAIPO4oiAYEWBIJaHMXCgP0TJdWklru0i b6jJSWa0hrUKrZfgMtTVfVVo/rlzYCpxrQxznVCfmDh/gBhDyNkTG0NjBNtUoq21rVsK Bu+uJk6s1SBl4W6sI+tAXF/0IWs55dSg2YZfs= MIME-Version: 1.0 Received: by 10.90.49.3 with SMTP id w3mr521160agw.120.1234452582394; Thu, 12 Feb 2009 07:29:42 -0800 (PST) In-Reply-To: References: <1404e5910902110834ld0af916vd49f96f47b653c39@mail.gmail.com> Date: Thu, 12 Feb 2009 10:29:42 -0500 Message-ID: <1404e5910902120729k118638fei1b85615da507ca5c@mail.gmail.com> From: Eric Covener To: users@httpd.apache.org Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org Subject: Re: [users@httpd] Threaded MPM + mod_php/mod_python/mod_perl/mod_ruby.. thread safe? On Thu, Feb 12, 2009 at 10:02 AM, howard chen wrote: > On Thu, Feb 12, 2009 at 12:34 AM, Eric Covener wrote: > >> Bizarre conclusion. Other interpreters are likely more >> thread-aware/thread-exploitative when not embedded in Apache, so >> they'd be less likely to casually link with non-threadsafe libraries. >> > > Why? Since if mod_php has thread safety problem with Apache2 worker > MPM, mod_python/mod_ruby should also have these problem, isn't? They're different code with different build systems. I don't think it immediately follows that they'd all have thread-safety problems. -- Eric Covener covener@gmail.com --------------------------------------------------------------------- The official User-To-User support forum of the Apache HTTP Server Project. See for more info. To unsubscribe, e-mail: users-unsubscribe@httpd.apache.org " from the digest: users-digest-unsubscribe@httpd.apache.org For additional commands, e-mail: users-help@httpd.apache.org