<?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>Fri, 24 May 2013 06:45:31 -0500</pubDate>
    <ttl>30</ttl>
    <item>
      <title><![CDATA[Wan Qi Chen: Background jobs with php and resque (Series)]]></title>
      <guid>http://www.phpdeveloper.org/news/18581</guid>
      <link>http://www.phpdeveloper.org/news/18581</link>
      <description><![CDATA[<p>
<i>Wan Qi Chen</i> has started a new series that looks at using PHP port of the <a href="https://github.com/defunkt/resque">resque</a> (a Ruby based tool) to do background processing for parts of his PHP applications - <a href="https://github.com/chrisboulton/php-resque">PHP-Resque</a>. So far, there's three parts to the series (with one more on the way):
</p>
<ul>
<li><a href="http://www.kamisama.me/2012/10/09/background-jobs-with-php-and-resque-part-1-introduction/">Part one</a> introduces the idea behind working with a background queue, the general workflow a process would follow and some of the benefits/drawbacks of using them.
<lI>In <a href="http://www.kamisama.me/2012/10/09/background-jobs-with-php-and-resque-part-2-queue-system/">part two</a> he gets more into the actual queue system and discusses the concept of a "job".
<li>The <a href="http://www.kamisama.me/2012/10/09/background-jobs-with-php-and-resque-part-3-installation/">third part</a> gets more into the implementation and helps you get the <a href="https://github.com/chrisboulton/php-resque">PHP-Resque</a>, <a href="https://github.com/nicolasff/phpredis">predis extension</a> and the <a href="http://www.php.net/manual/en/book.pcntl.php">process control extension</a> installed.
</ul>
<p>
The fourth part of the series (pending) will get into the actual code to implement this system you've job installed.
</p>]]></description>
      <pubDate>Wed, 10 Oct 2012 10:13:11 -0500</pubDate>
    </item>
  </channel>
</rss>
