On Thu, Apr 12, 2012 at 6:03 PM, Yasuo Ohgaki <yohg...@ohgaki.net> wrote:
> Hi, > > If we aren't going to consider saving current code risk, then > we could use both new include and file name convention. > > Introduce application/x-httpd-php-script, then we could > > AddHandler php5-script .php > AddType text/html .php > AddType application/x-httpd-php-source .phps > AddType application/x-httpd-php-script .ph // .phpp .phpc .phpscript > whatever extension here > Yeah that's more or less what I had in mind, actually. There'd be work involved, no question, but there's no reason why it shouldn't be doable. > > We may need ENV vars for other SAPIs. > I'm only familiar with installing PHP on Apache and IIS, so I honestly have no idea how it would work with other webservers. I'd wager that it's possible enough, but as for the "how," I'll have to defer to those who have experience working with said webserver(s). > > script/script_once for PHP only script includes. > Would the new "script" keyword behave like include or require? I'm very wary of the idea of having a special include to treat .php files the same as .phpp files, simply because it would seem to add a lot of complexity and potential for confusion, but I won't necessarily rule it out altogether, either. Right now I'm just working on reassuring those who are afraid this will cause every single framework on the internet to spontaneously combust lol. > > How about this? > > -- > Yasuo Ohgaki > yohg...@ohgaki.net >
