<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:ent="http://www.purl.org/NET/ENT/1.0/" version="2.0">
  <channel>
    <title>Curiouser and Curiouser! on REST</title>
    <link>http://matt.blogs.it/</link>
    <description>RSS feed for topic REST</description>
    <copyright>Copyright 2007 Matt Mower. Some rights reserved.</copyright>
    <generator>Squib/0.5.0.382</generator>
    <managingEditor>self@mattmower.com</managingEditor>
    <webMaster>self@mattmower.com</webMaster>
    <language>en-gb</language>
    <item>
      <title>That's good, I needed a REST</title>
      <link>http://matt.blogs.it/entries/00002583.html</link>
      <pubDate>Thu, 21 Jun 2007 09:40:12 +0100</pubDate>
      <description>&lt;p&gt;My copy of RESTful Web Services has turned up. Nothing terribly exciting in Chapters 1 and my skim of chapters 2 and 3 but I wasn't joined at the hip with SOAP so I didn't need much persuading. I've skipped ahead to Chapter 4 where we start talking about Resource Oriented Architectures. I've played with REST based Rails apps a couple of times and, when I had quite a simple structure ( e.g. weblog -&gt; articles ) it all seemed to make sense. In my last project the relationships were more complex and had more activities and it all became a little more jumbled. I'm hoping Richardson and Ruby and clear it up for me and present some useful guidelines for designing complex resource-oriented applications.&lt;/p&gt;</description>
      <guid isPermaLink="true">http://matt.blogs.it/entries/00002583.html</guid>
      <ent:cloud ent:href="http://matt.blogs.it/topics/">
      </ent:cloud>
    </item>
  </channel>
</rss>
