<?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, 23 May 2012 10:54:12 -0500</pubDate>
    <ttl>30</ttl>
    <item>
      <title><![CDATA[Lorna Mitchell's Blog: Add a heartbeat method to your service]]></title>
      <guid>http://www.phpdeveloper.org/news/13451</guid>
      <link>http://www.phpdeveloper.org/news/13451</link>
      <description><![CDATA[<p>
<i>Lorna Mitchell</i> has a <a href="http://www.lornajane.net/posts/2009/Add-a-heartbeat-method-to-your-service">last minute suggestion</a> of something to add to your web service that can really help out when developers using the API need it - a heartbeat.
</p>
<blockquote>
The heartbeat shouldn't require any particular parameters or any authentication, since formatting data and passing credentials can be a stumbling block for those integrating with a service for the first time or those debugging issues. The heartbeat method can return some known data, perhaps an "I'm here" message, and maybe some version information.
</blockquote>
<p>
She points out Flickr's <a href="http://www.flickr.com/services/api/flickr.test.echo.html">flickr.test.echo</a> call that does nothing but return whatever was sent to it. This kind of method can be very useful for applications that might need constant contact with the API or, inversely, need to know when the API isn't there and switch to an offline mode. A consistent heartbeat makes it easy to check these sort of things and to be sure that you get consistent feedback from your requests.
</p>]]></description>
      <pubDate>Thu, 29 Oct 2009 08:41:53 -0500</pubDate>
    </item>
  </channel>
</rss>

