Re: Re: output handlers
| From: | Zeev Suraski | Date: | Tue, 06 Aug 2002 13:49:01 +0000 |
| Subject: | Re: Re: output handlers | ||
| References: | 1 2 3 | Groups: | php.cvs php.dev php.dev |
| Request: | Send a blank email to php-cvs+get-13176@lists.php.net to get a copy of this message | ||
At 17:00 06/08/2002, Yasuo Ohgaki wrote:
Zeev Suraski wrote:I'm very much against configuration options that affect the way the language behaves; But supplying server-wide settings that allow you to deploy your site in a certain way are a good thing in my opinion. They should also be transparent to well-written applications. Why would an I18N app not work with output_handler? ZeevI haven't noticed this discussion before, but I'm very much againstDon't worry you haven't miss much.removing or deprecating output_handler. If you want to write a portable app, you should indeed register output handlers in your app; But generally speaking, output handlers are functions which are very likely to be implemented on a site-wide basis, and not necessarily a script- or app-wide basis. For such purposes, php.ini is the right place.Ok. You are asking for trouble and some people criticize "PHP is endlessly configurable by php.ini" :(