At 00:25 24/03/2010, Antony Dovgal wrote:
On 24.03.2010 01:08, Zeev Suraski wrote:
> At 23:58 23/03/2010, Antony Dovgal wrote:
>>Okay, here is XML based config quickly converted to php.ini-style syntax:
>
> Here's mine - a bit more representative of how .ini files look
> instead of trying to convert a nested XML file:
I'm sure you understand that nesting makes things much more easier to read.
Only if it's really necessary, which doesn't appear to be the case here.
fpm.workers.<pool name ASCII only and no
spaces>.pm.dynamic.start_servers is not my preferred syntax.
I find the .ini version (the one I submitted) way, way easier to read
- it's designed for humans and requires no parsing. I don't see why
we need to add fpm.workers.poolname.pm.dynamic, where fpm.workers is
obvious, and poolname is in the section name. You're left with
pm.dynamic - which is fine.
And yes, this is how it should look like since you're implying that FPM config
should be a part of php.ini (otherwise I don't see how these two
different files are related at all).
I'm not implying it, in fact I'm downright saying *the opposite*. It
should be in its own fpm.ini file, using .ini syntax. It shouldn't
use PHP's INI subsystem since it's irrelevant to it, and we may want
to implement special handling for certain directive names (e.g.
includes, should we decide to implement them).
All along I was talking about the syntax, not php.ini itself.
Zeev
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
