<?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>Sun, 12 Feb 2012 20:16:31 -0600</pubDate>
    <ttl>30</ttl>
    <item>
      <title><![CDATA[Lorna Mitchell's Blog: Status Codes for Web Services]]></title>
      <guid>http://www.phpdeveloper.org/news/12805</guid>
      <link>http://www.phpdeveloper.org/news/12805</link>
      <description><![CDATA[<p>
<i>Lorna Mitchell</i> has posted <a href="http://www.lornajane.net/posts/2009/Status-Codes-for-Web-Services">the last article</a> in her look at web services - a focus on status codes.
</p>
<blockquote>
Unlike the other posts in this series, this one is quite specific to one type of service - REST - since it deals with status codes, specifically HTTP ones. The ideas are transferrable however and other types of service can return statuses in a similar way.
</blockquote>
<p>
She mentions things to keep in mind in returning the codes, some of the more interesting codes as well as some typical situations where things like an error code 500 would be thrown.
</p>
<blockquote>
Status codes are like a headline to the calling entity about what happened, and are a valuable tool in the web service toolkit.
</blockquote>]]></description>
      <pubDate>Fri, 03 Jul 2009 15:44:37 -0500</pubDate>
    </item>
  </channel>
</rss>

