<?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, 19 Jun 2013 16:47:38 -0500</pubDate>
    <ttl>30</ttl>
    <item>
      <title><![CDATA[Jeremy Brown's Blog: 3 Tenets for Implementing a REST API]]></title>
      <guid>http://www.phpdeveloper.org/news/16066</guid>
      <link>http://www.phpdeveloper.org/news/16066</link>
      <description><![CDATA[<p>
<i>Jeremy Brown</i>, after working tirelessly on a REST API based around the Zend Framework (and a few other technologies), has come up with his <a href="http://www.notmessenger.com/rest/3-tenets-for-implementing-a-rest-api/">three tenets for implementing a REST API</a> to hopefully help you along the straight and narrow path that he forged himself.
</p>
<blockquote>
In the course of performing my duties at my day job I recently came across the need for our data to be accessible via an API. After researching the various types available, I settled on developing a REST API. The selection process wasn't the interesting part of this exercise though. Actually implementing a REST API is what was.
</blockquote>
<p>
His advice ranges from the general to very specific, sharing tips on how to most effectively create the service's API:
</p>
<ul>
<li>REST is a set of principles (and not a specification)
<li>Do not use custom media types
<li>Represent the headers in the response payload
</ul>]]></description>
      <pubDate>Fri, 18 Mar 2011 09:17:05 -0500</pubDate>
    </item>
  </channel>
</rss>
