<?xml version="1.0" encoding="utf-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" version="2.0">
  <channel>
    <title><![CDATA[Content with Style - Comments on REST and some unknown verbs]]></title>
    <link>http://www.contentwithstyle.co.uk/feeds/rss/comments/111</link>
    <description><![CDATA[]]></description>
    <pubDate>Tue, 06 Jan 2009 04:33:31 +0000</pubDate>
    <generator>Zend_Feed</generator>
    <docs>http://blogs.law.harvard.edu/tech/rss</docs>
    <item>
      <title><![CDATA[Content with Style - Comment #1 on REST and some unknown verbs]]></title>
      <link>http://www.contentwithstyle.co.uk/content/rest-and-some-unknown-verbs/#comment-942</link>
      <guid>http://www.contentwithstyle.co.uk/content/rest-and-some-unknown-verbs/#comment-942</guid>
      <description><![CDATA[Pretty interesting read that &#8220;How I explained REST to my wife&#8221;. It reminds me of the Atom Publishing Protocol which is currently a draft at the IETF  which is using GET, PUT, POST, and DELETE everywhere in order to manage ressources. It&#8217;s true that these verbs aren&#8217;t used as much as they should, and that&#8217;s probably because everyone has been busy working within the limitations of the browser. You can&#8217;t PUT, or DELETE from a browser.]]></description>
      <content:encoded><![CDATA[Pretty interesting read that &#8220;How I explained REST to my wife&#8221;. It reminds me of the Atom Publishing Protocol which is currently a draft at the IETF  which is using GET, PUT, POST, and DELETE everywhere in order to manage ressources. It&#8217;s true that these verbs aren&#8217;t used as much as they should, and that&#8217;s probably because everyone has been busy working within the limitations of the browser. You can&#8217;t PUT, or DELETE from a browser.]]></content:encoded>
      <pubDate>Tue, 27 Jun 2006 21:25:05 +0000</pubDate>
    </item>
    <item>
      <title><![CDATA[Content with Style - Comment #2 on REST and some unknown verbs]]></title>
      <link>http://www.contentwithstyle.co.uk/content/rest-and-some-unknown-verbs/#comment-945</link>
      <guid>http://www.contentwithstyle.co.uk/content/rest-and-some-unknown-verbs/#comment-945</guid>
      <description><![CDATA[Unfortunately, too many web &#8220;experts&#8221; are oblivious to the less common REST methods. I&#8217;ve been using them for years, and ensure all my apps are coded in a REST-ful way.<br />
<br />
Seems as though its made my life <em>much</em> easier, as I don&#8217;t think about the same problems as most people when developing.<br />
<br />
One thing to remember about the difference between PUT and POST &#8211; PUT does exactly what it says on the tin &#8211; it is supposed to PUT a resource onto the server/target. Simple.<br />
<br />
POST, however, has become confused. Essentially, it is meant to POST an update to the server, updating a specific resource, a list, or database. Its meant as a catch-all when one of the other methods won&#8217;t do. <br />
<br />
So, to PUT something, you&#8217;d use &lt;form method=&#8221;put&#8221; action=&#8221;/path/to/resource/dir/&#8221;&gt;... whereas POST would point to the resource to be updated: &lt;form method=&#8221;post&#8221; action=&#8221;/path/to/resource.ext&#8221;&gt;<br />
<br />
However, just like GET, it has become misused by the web community at large. Just like some developers use GET to post updated information to a server (causing a whole host of problems with web &#8220;caching&#8221; software &#8211; see google cache), they use POST to put a new resource online.<br />
<br />
Lets hope this practice is forgotten sooner rather than later.<br />
<br />
One of the more useful methods of REST is HEAD, where you can get information about a resource without actually GETting the resource. This is useful in confirming updates/changes to a file made from another source or finding out whether a resource exists before updating it.<br />
<br />
A really useful resource is the HTTP/1.1 spec:<br />
http://www.faqs.org/rfcs/rfc2616<br />
This gives you information on all the HTTP methods, plus all the response codes that can be issued/expected from the server.<br />
<br />
If you&#8217;re interested, refactored is a RESTful framework I&#8217;m developing which has a few additional features not seen in most frameworks&#8230; keep your eye out for its first release!]]></description>
      <content:encoded><![CDATA[Unfortunately, too many web &#8220;experts&#8221; are oblivious to the less common REST methods. I&#8217;ve been using them for years, and ensure all my apps are coded in a REST-ful way.<br />
<br />
Seems as though its made my life <em>much</em> easier, as I don&#8217;t think about the same problems as most people when developing.<br />
<br />
One thing to remember about the difference between PUT and POST &#8211; PUT does exactly what it says on the tin &#8211; it is supposed to PUT a resource onto the server/target. Simple.<br />
<br />
POST, however, has become confused. Essentially, it is meant to POST an update to the server, updating a specific resource, a list, or database. Its meant as a catch-all when one of the other methods won&#8217;t do. <br />
<br />
So, to PUT something, you&#8217;d use &lt;form method=&#8221;put&#8221; action=&#8221;/path/to/resource/dir/&#8221;&gt;... whereas POST would point to the resource to be updated: &lt;form method=&#8221;post&#8221; action=&#8221;/path/to/resource.ext&#8221;&gt;<br />
<br />
However, just like GET, it has become misused by the web community at large. Just like some developers use GET to post updated information to a server (causing a whole host of problems with web &#8220;caching&#8221; software &#8211; see google cache), they use POST to put a new resource online.<br />
<br />
Lets hope this practice is forgotten sooner rather than later.<br />
<br />
One of the more useful methods of REST is HEAD, where you can get information about a resource without actually GETting the resource. This is useful in confirming updates/changes to a file made from another source or finding out whether a resource exists before updating it.<br />
<br />
A really useful resource is the HTTP/1.1 spec:<br />
http://www.faqs.org/rfcs/rfc2616<br />
This gives you information on all the HTTP methods, plus all the response codes that can be issued/expected from the server.<br />
<br />
If you&#8217;re interested, refactored is a RESTful framework I&#8217;m developing which has a few additional features not seen in most frameworks&#8230; keep your eye out for its first release!]]></content:encoded>
      <pubDate>Wed, 28 Jun 2006 02:57:09 +0000</pubDate>
    </item>
    <item>
      <title><![CDATA[Content with Style - Comment #3 on REST and some unknown verbs]]></title>
      <link>http://www.contentwithstyle.co.uk/content/rest-and-some-unknown-verbs/#comment-947</link>
      <guid>http://www.contentwithstyle.co.uk/content/rest-and-some-unknown-verbs/#comment-947</guid>
      <description><![CDATA[While most browsers and server plateforms supports the 4 HTTP verbs, it is not always easy to find good information on how to use them. <br />
<br />
For instance, PHP assumes that a POST always contains form data  ($_POST is an associative array of field name/value pairs). If you want to POST something that is not a a form (a XML document for instance), you&#8217;ll have to resort to the rather obscure file_get_contents(&#8216;php://input&#8217;)  to get the raw data from the POST request.<br />
<br />
Also, you may want to take a look at Freja ( http://www.csscripting.com/Freja ) &#8211; Framework for REstful Javascript Applications.<br />
<br />
Applications built on Freja:<br />
1. Run in the browser. <br />
2. Use XML for data and DOM for data manipulation.<br />
3. Use XSL for interface templates and client-side XSLT for interface rendering.<br />
4. Are server-side agnostic. They communicate with RESTful web services using asynchronous HTTP requests.  PUT and DELETE verbs are supported since version 2.0<br />
<br />
Freja is not a server-side framework but there are a couple sample server-side scripts that show how to build PHP RESTful web services]]></description>
      <content:encoded><![CDATA[While most browsers and server plateforms supports the 4 HTTP verbs, it is not always easy to find good information on how to use them. <br />
<br />
For instance, PHP assumes that a POST always contains form data  ($_POST is an associative array of field name/value pairs). If you want to POST something that is not a a form (a XML document for instance), you&#8217;ll have to resort to the rather obscure file_get_contents(&#8216;php://input&#8217;)  to get the raw data from the POST request.<br />
<br />
Also, you may want to take a look at Freja ( http://www.csscripting.com/Freja ) &#8211; Framework for REstful Javascript Applications.<br />
<br />
Applications built on Freja:<br />
1. Run in the browser. <br />
2. Use XML for data and DOM for data manipulation.<br />
3. Use XSL for interface templates and client-side XSLT for interface rendering.<br />
4. Are server-side agnostic. They communicate with RESTful web services using asynchronous HTTP requests.  PUT and DELETE verbs are supported since version 2.0<br />
<br />
Freja is not a server-side framework but there are a couple sample server-side scripts that show how to build PHP RESTful web services]]></content:encoded>
      <pubDate>Wed, 28 Jun 2006 09:37:55 +0000</pubDate>
    </item>
    <item>
      <title><![CDATA[Content with Style - Comment #4 on REST and some unknown verbs]]></title>
      <link>http://www.contentwithstyle.co.uk/content/rest-and-some-unknown-verbs/#comment-952</link>
      <guid>http://www.contentwithstyle.co.uk/content/rest-and-some-unknown-verbs/#comment-952</guid>
      <description><![CDATA[Dude, I went through the same thing like two months ago with REST. I hate acronyms.]]></description>
      <content:encoded><![CDATA[Dude, I went through the same thing like two months ago with REST. I hate acronyms.]]></content:encoded>
      <pubDate>Thu, 29 Jun 2006 10:35:13 +0000</pubDate>
    </item>
    <item>
      <title><![CDATA[Content with Style - Comment #5 on REST and some unknown verbs]]></title>
      <link>http://www.contentwithstyle.co.uk/content/rest-and-some-unknown-verbs/#comment-954</link>
      <guid>http://www.contentwithstyle.co.uk/content/rest-and-some-unknown-verbs/#comment-954</guid>
      <description><![CDATA[I had no idea about PUT or DELETE! Never heard of them and never used them&#8230; Since I don&#8217;t do much server side development I shouldn&#8217;t be all that surprised that I&#8217;ve not used them but, like Pascal, I can&#8217;t believe that I&#8217;ve never even heard of them!]]></description>
      <content:encoded><![CDATA[I had no idea about PUT or DELETE! Never heard of them and never used them&#8230; Since I don&#8217;t do much server side development I shouldn&#8217;t be all that surprised that I&#8217;ve not used them but, like Pascal, I can&#8217;t believe that I&#8217;ve never even heard of them!]]></content:encoded>
      <pubDate>Thu, 29 Jun 2006 15:51:29 +0000</pubDate>
    </item>
    <item>
      <title><![CDATA[Content with Style - Comment #6 on REST and some unknown verbs]]></title>
      <link>http://www.contentwithstyle.co.uk/content/rest-and-some-unknown-verbs/#comment-974</link>
      <guid>http://www.contentwithstyle.co.uk/content/rest-and-some-unknown-verbs/#comment-974</guid>
      <description><![CDATA[Michel:<br />
Actually, some Browsers do support PUT and DELETE as well, at least using javascript&#8217;s xmlhttprequest. As far as I know are Mozilla based browsers and IE perfectly fine with it. Not sure about Opera, but I know that Safari doesn&#8217;t like it.<br />
<br />
Also, php&#8217;s php://input will happily accept any sent information in POST as well as PUT and DELETE. I&#8217;m sure HEAD is fine, too.]]></description>
      <content:encoded><![CDATA[Michel:<br />
Actually, some Browsers do support PUT and DELETE as well, at least using javascript&#8217;s xmlhttprequest. As far as I know are Mozilla based browsers and IE perfectly fine with it. Not sure about Opera, but I know that Safari doesn&#8217;t like it.<br />
<br />
Also, php&#8217;s php://input will happily accept any sent information in POST as well as PUT and DELETE. I&#8217;m sure HEAD is fine, too.]]></content:encoded>
      <pubDate>Tue, 04 Jul 2006 09:40:12 +0000</pubDate>
    </item>
  </channel>
</rss>
