<?xml version="1.0"?>
<rss version="2.0">
  <channel>
    <title>PHPDeveloper.org</title>
    <link>http://www.phpdeveloper.org</link>
    <description>Up-to-the Minute PHP News, views and community</description>
    <language>en-us</language>
    <pubDate>Wed, 22 May 2013 22:15:38 -0500</pubDate>
    <ttl>30</ttl>
    <item>
      <title><![CDATA[Ole Markus With's Blog: Experimenting with uWSGI and its PHP plugin]]></title>
      <guid>http://www.phpdeveloper.org/news/18124</guid>
      <link>http://www.phpdeveloper.org/news/18124</link>
      <description><![CDATA[<p>
In a <a href="http://barelysufficient.org/2012/06/experimenting-uwsgi-php-plugin/">recent post to his blog</a> <i>Ole Markus With</i> looks at using the <a href="http://projects.unbit.it/uwsgi">uWSGI</a> server to serve up PHP applications that works similarly to the <a href="http://us2.php.net/manual/en/install.fpm.php">FastCGI Process Manager</a> that's included with PHP.
</p>
<blockquote>
If we ignore the additional features, using uWSGI with PHP is somewhat equivalent to using the <a href="http://us3.php.net/manual/en/install.fpm.php">Process Manager (FPM)</a> that ships with PHP. Just like FPM, the concept is that PHP runs inside a server dedicated to handling the processes/threads running the PHP code. This in contrast to running PHP inside of the actual webserver, like Apache's Mod_PHP, or letting the webserver handle the process management, like lighttpd typically does. In other words, you have the following chain of services: Client -> webserver -> process manager -> PHP interpreter.
</blockquote>
<p>
He includes some information about the setup ("is it easy?") and how it's more application-based than the usual PHP setup. He also touches on two other larger concerns - is it faster than some of the alternatives and whether or not you should spend time in your day to look into it.
</p>]]></description>
      <pubDate>Thu, 21 Jun 2012 12:06:34 -0500</pubDate>
    </item>
  </channel>
</rss>
