Mailing-List: contact modperl-help@perl.apache.org; run by ezmlm
Precedence: bulk
Message-ID: <20040608224731.67740.qmail@web52802.mail.yahoo.com>
Date: Tue, 8 Jun 2004 15:47:31 -0700 (PDT)
From: Chris Shiflett <shiflett@php.net>
Reply-To: shiflett@php.net
Subject: Re: mod_perl presence at OSCON (and other CONs) is at danger
To: Perrin Harkins <perrin@elem.com>, Stefan Loones <stefv@pandava.com>
Cc: Modperl List <modperl@perl.apache.org>
In-Reply-To: <1086731003.28027.37.camel@localhost.localdomain>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii

--- Perrin Harkins <perrin@elem.com> wrote:
> If you notice, no one talks about mod_php. Instead they talk about
> PHP.

Well, there are a few reasons for that, and none of them have to do with
PR really.

First, PHP was not created as a general-purpose scripting language. There
is now a command-line interpreter (I'm sure the thought of shell scripts
written in PHP make some of you shudder), but it wasn't there until
recently. In fact, referencing this is very clumbsy, and most people call
it the PHP CLI. So, it gives us something like this:

Perl:mod_perl::PHP CLI:PHP

Another reason for the naming habits is that PHP runs on more Web servers
than Apache, and only the Apache SAPI is called mod_php. And, because
mod_php doesn't implement the full Apache API (another rarely-used and
experimental SAPI called apache_hooks does), there isn't anything
significant to distinguish mod_php from any other the other SAPIs, so
you'll almost never see it referenced in conversation.

Anyway, there's a PHP guy's perspective.

Chris

-- 
Report problems: http://perl.apache.org/bugs/
Mail list info: http://perl.apache.org/maillist/modperl.html
List etiquette: http://perl.apache.org/maillist/email-etiquette.html