Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:52563
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: error (pb1.pair.com: domain roshambo.org from 209.85.210.42 cause and error)
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=us-ascii
In-Reply-To: <BANLkTimXifjrWmoS9LvhjbYQMw1et9TS2Q@mail.gmail.com>
Date: Tue, 31 May 2011 06:57:36 -0700
Cc: Kalle Sommer Nielsen <kalle@php.net>,
 marius adrian popa <mapopa@gmail.com>,
 PHP Developers Mailing List <internals@lists.php.net>
Content-Transfer-Encoding: quoted-printable
Message-ID: <36AF85D9-01D5-43B0-9456-A288E740A85B@roshambo.org>
References: <BANLkTinXAa6KGc6SfTtWU7JgZJ1iSOGMcg@mail.gmail.com> <BANLkTinVogAxMoo7cdj-goaGy0c2J1ROyg@mail.gmail.com> <BANLkTimXifjrWmoS9LvhjbYQMw1et9TS2Q@mail.gmail.com>
To: Daniel Brown <danbrown@php.net>
Subject: Re: [PHP-DEV] removing some cruft
From: philip@roshambo.org (Philip Olson)


On May 28, 2011, at 10:42 AM, Daniel Brown wrote:

> On Sat, May 28, 2011 at 06:05, Kalle Sommer Nielsen <kalle@php.net> =
wrote:
>>=20
>> expose_php =3D Off?
>=20
>    I think what he and others mean is that they want the option to
> leave the logo, credits, et cetera, completely out of the build at
> compile time.

We also have other possibilities here (this is not a proposal, but =
rather, a list of options/ideas to ponder):

0. Do nothing

1. Disable expose_php within the distributed php.ini-* files

Trivial, but changing [at least] php.ini-production is a real =
possibility.

2. Disable expose_php by default within PHP

We could do this too. Default =3D=3D=3D when no php.ini file is used.

3. Remove the specific PHP version from the exposed PHP header

There are security concerns although I'm not sure what implications =
(BC?) or real help this would offer. For example, version information =
can be deciphered by other means (e.g., logos and credits change over =
time) but maybe it's a help because, for example, displaying phpinfo() =
requires direct user action. See also #4.

4. Change its behavior and usage

For example, phpinfo() relies upon expose_php for both the logo and =
credits information to be displayed. However, the phpinfo() output =
clearly exposes PHP (along with the version) regardless of the =
expose_php setting so we could instead embed the logo into phpinfo(), =
and display credits as per phpcredits(), instead of relying upon =
expose_php for this as done currently. In other words, expose_php could =
be off yet phpinfo() behavior would remain close to the same with either =
a little extra markup, or appended credits near the license.

But this raises the question: Why do we have magical logo and credit =
guids?

5. And a performance review

People are concerned with performance issues (e.g., images loaded into =
memory) although I'm not sure what real performance is lost (some have =
made guesses). Is there a real issue with performance here? How does it =
compare with, let's say, loading an additional extension? If so, how can =
it be helped?

Regards,
Philip