Re: Re: utf-8?q?svn:_/php/php-src/trunk/sapi/fpm/_config.m4_fpm/fastcgi.c_ fpm/fpm=5Fchildren.c_fpm/fpm=5Fconf.c_fpm/fpm=5Fconf.h_fpm/fpm=5Fenv.c_fpm
/fpm=5Fphp.c_fpm/fpm=5Fprocess=5Fctl.c_fpm/fpm=5Fsockets.c_fpm/fpm=5Fstatu s.c_fpm/fpm=5Fu

Le 23 avril 2010 13:09, Derick Rethans <derick@php.net> a écrit : > On Fri, 23 Apr 2010, Jérôme Loyet wrote: > >> Le 23 avril 2010 11:31, Derick Rethans <derick@php.net> a écrit : >> > On Wed, 21 Apr 2010, Jérôme Loyet wrote: >> >> >> >> Log: >> >> switch the configuration syntax from xml to ini >> >> It's been describe in the RFC: >> >> http://wiki.php.net/rfc/fpm/ini_syntax >> >> > I feel extremely unhappy about this patch. From what I've seen there >> > is only a very small group of people that want to switch from the >> > XML format to the INI format. Another group, was opposed to this >> > move. I for one, find this new INI stuff extremely complicated and >> > annoying. >> >> Please compare http://www.fatbsd.com/fpm/php-fpm.conf.ini >> and >> http://www.fatbsd.com/fpm/php-fpm.conf.xml >> Those 2 files have exactly the same values. >> >> root@raptor> wc php-fpm.conf.* >>       33      28     683 php-fpm.conf.ini >>       48      77    1554 php-fpm.conf.xml >> >> Number of lines: 32% less lines in INI than XML >> Number of words: 64% less words in INI than XML >> Numbers of bytes: 57% less bytes in INI than XML >> >> Do you really think XML is easier to read/right than INI ? > > Conciseness has never been a synonym for readability. > > The structured approach of the XML makes it much easier to see exactly > which value belongs to which section. in php-fpm there is only one level of section. One section == One pool. That's all In the current XML syntax there is several level of section which are total useless. They have been removed in INI. > >> > Instead of a nice ordered XML file we now have a mess of INI files >> > that makes me think of Windows 3.11. >> >> So in your mind you want the php.ini to be changed to xml (php.xml) ? > > No, they are two different things. php.ini doesn't need sections, or > nested structures whereas the FPM configuration benefits from it > so that you can see immediately to which part a specific configuration > setting belongs. > > There are two totally different uses of configuration files here, so > there is no reason to jump through hoops to make them look a little bit > the same and introducing lots of complexity at the same time. It's even > more ridiculous because the original XML configuration format was > working just fine. > > regards, > Derick > > -- > http://derickrethans.nl | > http://xdebug.org > Like Xdebug? Consider a donation: http://xdebug.org/donate.php > twitter: @derickr and @xdebug > > -- > PHP CVS Mailing List (http://www.php.net/) > To unsubscribe, visit: http://www.php.net/unsub.php >