@saj - really? You think mod_php is falling out of favor? That is quite a statement... one that I can't imagine is true. PHP is one of the most ubiquitous web scripting languages, second only to Perl. A cannot imagine hosts degrading their support for this language....
Well, my evidence is anecdotal - one specific host. My main point, however, is that mod_perlite is likely to run into the same problems with multiple users running code within the same Apache module. Specifically, performance monitoring is difficult because you cannot pinpoint which user's code may be causing problems. Also, one user's code may be able to exploit security holes to access another user's data. Of course, PHP isn't known for having the best code base so perhaps you guys can do a better job of finding solutions to these problems....
@saj - It's interesting you bring these things up because Aaron and I were just talking about what we could do to make the module more appealing to hosting providers - especially in regards to monitoring and process/thread control. Do you think hosting providers are simply interested in monitoring or doing resource control around specific realms/domains?...
@Roey - It is great to hear you were so successful in deploying FastCGI. What is so remarkable in my personal experience is how variable the ease of installation can be. I have been on some systems where FastCGI is a "yum update" or "apt-get" away, and then on some systems where FastCGI causes Apache to segfault constantly, and others where the prerequisites were virtually impossible to satisfy. It is so unpredictable. And that is one of the experiences informing and motivating the mod_perlite project. Because nothing should be that difficult or unpredictable to install....
DEPRECATION WARNING: Use of $app->param to get/set query object properties in MT::App::Community at line 38 will break in the future. Use $app->query->param() instead.
DEPRECATION WARNING: Use of $app->param to get/set query object properties in MT::App::Community at line 1819 will break in the future. Use $app->query->param() instead.
DEPRECATION WARNING: Use of $app->param to get/set query object properties in MT::App::Community at line 1820 will break in the future. Use $app->query->param() instead.
DEPRECATION WARNING: Use of $app->param to get/set query object properties in MT::App::Community at line 1821 will break in the future. Use $app->query->param() instead.
DEPRECATION WARNING: Use of $app->param to get/set query object properties in CustomFields::Util at line 128 will break in the future. Use $app->query->param() instead.
DEPRECATION WARNING: Use of $app->param to fetch the CGI query object in CustomFields::Util at line 133 will break in the future. Use $app->query instead.
Comment Threads
Subscribe to Comment Thread Feed"