For #2 it might no longer be needed that might be up for debate. It's
nice to be able to override a single option. But 5.3 with it's
htaccess/htscanner behavior might work good enough for most things
(but PHP_INI_SYSTEM might be still nice to override one offs instead
of having to point to a totally separate ini file) unless you say that
there is a global ini file with defaults and the per-pool override is
just overrides for that.
As for #1 we are working on changing the config file syntax and the
idea was to make it use nginx style. I don't think it will fit in ini
file format as it needs arrays or some sort of n+1 group structure
support/nested options.
IIRC array support did just get inplemented in 5.3 did it not? That -
may- be an option then. Then fpm could actually share php.ini itself.
I guess it depends on if the ini support php has will work well with
nested groupings.
Sent from my iPhone
On Dec 7, 2009, at 10:49 AM, Stanislav Malyshev <s...@zend.com> wrote:
Hi!
Couple of other notes here:
1. I understand this SAPI uses its own XML config format. While it
is not unheard of for SAPIs to integrate into external servers and
thus have diferent config ways, this one is self contained - so I
wonder if it would be possible to make it configured by .ini? We
have .ini parser, people know what .ini format is, etc.
2. Do we need <value name="php_defines"> if we already have user ini
files?
--
Stanislav Malyshev, Zend Software Architect
s...@zend.com http://www.zend.com/
(408)253-8829 MSN: s...@zend.com
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
