Re: FPM RFC

At 00:33 24/03/2010, Derick Rethans wrote:

On Wed, 24 Mar 2010, Zeev Suraski wrote: At 00:01 24/03/2010, Derick Rethans wrote:

I don't see how this actually matters. None of the other SAPIs are configured with a php.ini syntax.

None of the other SAPIs are configured, period. That's not true. You configure the fastcgi SAPI for lighttpd in the lighttpd config, in LUA. Sure, it's the web-server side of it, but it's no different from sapi/fpm which is its own little wrapper instead of the one that comes with lighttpd.

I think it's very different. Would we include that LUA code in PHP? That's the difference. It's going to become a part of PHP, it's going to be supported by PHP, it should use the same mechanisms as the rest of PHP.

My take on this is: - Add sapi/fpm to trunk; it's standalone, it works - If somebody finds it necessary, write the code for it and we can discuss whether we actually want a .ini file like syntax.

I think there was substantial opposition to keeping the XML-based configuration file. The obvious default was .ini-syntax, and now that it's clear it's very much a viable option - I think we should go for it. I think keeping it as XML and then putting the burden of moving it to another format the many people that commented on the RFC - after they write the code, no less - is not reasonable. My take: - Put it in trunk, subject to change in the configuration file format before it gets released. Principals aside, I can take care of moving it to .ini format. Zeev