<?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>Thu, 23 May 2013 22:51:01 -0500</pubDate>
    <ttl>30</ttl>
    <item>
      <title><![CDATA[Michael Kimsal's Blog: Joe Stump @ MySQL]]></title>
      <guid>http://www.phpdeveloper.org/news/9997</guid>
      <link>http://www.phpdeveloper.org/news/9997</link>
      <description><![CDATA[<p>
On his blog, <i>Michael Kimsal</i> <a href="http://michaelkimsal.com/blog/joe-stump-mysql/">talks about</a> a presentation he sat in on at this year's <a href="http://www.mysqlconf.com/">MySQL Conference</a> given by <i>Joe Stump</i> from Digg.com:
</p>
<blockquote>
One key thing he's repeating is using a service layer to access data asynchronously.  His advice right now is to group data requests at the top of a user request, do them asynchronously, and then use the data in the rendering when it comes back. 
</blockquote>
<p>
They've <a href="http://pear.php.net/package/Services_Digg/">published a PEAR package</a> as an example of this asynchronous method that interfaces with Digg's API (http://services.digg.com). You can read more about the subject of his talk on <a href="http://en.oreilly.com/mysql2008/public/schedule/detail/468">the MySQL Conference website</a>.
</p>]]></description>
      <pubDate>Fri, 18 Apr 2008 12:09:57 -0500</pubDate>
    </item>
  </channel>
</rss>
