<?xml version="1.0" encoding="UTF-8"?><!-- generator="WordPress/2.9.1" -->
<rss version="0.92">
<channel>
	<title>Untangled</title>
	<link>http://roy.gbiv.com/untangled</link>
	<description>musings of Roy T. Fielding</description>
	<lastBuildDate>Thu, 14 May 2009 02:07:58 +0000</lastBuildDate>
	<docs>http://backend.userland.com/rss092</docs>
	<language>en</language>
	
	<item>
		<title>Wrangling mime.types</title>
		<description><![CDATA[One of the chores that I do for the Apache HTTP server project, every three months or so, is to slog through the IANA media type registry to see what new media types have been registered and add them to the mime.types configuration file. This is one of the few things I do that is [...]]]></description>
		<link>http://roy.gbiv.com/untangled/2009/wrangling-mimetypes</link>
			</item>
	<item>
		<title>It is okay to use POST</title>
		<description><![CDATA[Tim Bray&#8217;s article on RESTful Casuistry revisits an odd meme in the REST debates that I&#8217;ve been meaning to discredit for a while.
Some people think that REST suggests not to use POST for updates.  Search my dissertation and you won&#8217;t find any mention of CRUD or POST. The only mention of PUT is in regard [...]]]></description>
		<link>http://roy.gbiv.com/untangled/2009/it-is-okay-to-use-post</link>
			</item>
	<item>
		<title>Specialization</title>
		<description><![CDATA[As you may have noted, my last post seems to have hit a nerve in various communities, particularly with those who are convinced that REST means HTTP (because, well, that&#8217;s what they think it means) and that any attempt by me to describe REST with precision is just another elitist philosophical effort that won&#8217;t apply [...]]]></description>
		<link>http://roy.gbiv.com/untangled/2008/specialization</link>
			</item>
	<item>
		<title>REST APIs must be hypertext-driven</title>
		<description><![CDATA[I am getting frustrated by the number of people calling any HTTP-based interface a REST API. Today&#8217;s example is the SocialSite REST API. That is RPC. It screams RPC. There is so much coupling on display that it should be given an X rating.
What needs to be done to make the REST architectural style clear [...]]]></description>
		<link>http://roy.gbiv.com/untangled/2008/rest-apis-must-be-hypertext-driven</link>
			</item>
	<item>
		<title>No REST in CMIS</title>
		<description><![CDATA[About three weeks ago, a new &#8220;standard&#8221; for Content Management Interoperability Services (CMIS) was announced by EMC, IBM, and Microsoft with the usual fanfare of being the best thing since sliced bread and compliant with the latest buzzwords. One of those buzzwords, REST (as in Representational State Transfer), happens to be defined by my dissertation. [...]]]></description>
		<link>http://roy.gbiv.com/untangled/2008/no-rest-in-cmis</link>
			</item>
	<item>
		<title>Economies of scale</title>
		<description><![CDATA[I need to address that teaser I included in my last post on paper tigers and hidden dragons:
People need to understand that general-purpose PubSub is not a solution to scalability problems — it simply moves the problem somewhere else, and usually to a place that is inversely supported by the economics.
I am talking here about [...]]]></description>
		<link>http://roy.gbiv.com/untangled/2008/economies-of-scale</link>
			</item>
	<item>
		<title>Paper tigers and hidden dragons</title>
		<description><![CDATA[One of the sessions that I attended at OSCON was “Beyond REST? Building Data Services with XMPP PubSub” by Evan Henshaw-Plath and Kellan Elliott-McCrea. I think you can guess why that made me curious, but it was interesting to see how much that curiosity was shared by the rest of the conference: the room filled [...]]]></description>
		<link>http://roy.gbiv.com/untangled/2008/paper-tigers-and-hidden-dragons</link>
			</item>
	<item>
		<title>Off the wagon</title>
		<description><![CDATA[Hmm, over five months since my last (published) post. I don&#8217;t know how folks like Tim and Sam keep writing every day. I&#8217;ll have to ask when I see them at ApacheCon US in New Orleans.
I fell off the blogon while trying to prepare my two presentations for ApacheCon Europe and have yet to catch [...]]]></description>
		<link>http://roy.gbiv.com/untangled/2008/off-the-wagon</link>
			</item>
	<item>
		<title>Information networks</title>
		<description><![CDATA[One of the keys to understanding how the Web works is to understand how social networks impact the structure of information (and vice versa). Jon Kleinberg at Cornell University has organized a couple great courses on the subject, at both the undergraduate and graduate levels. One of these days, I&#8217;ll find the time to (re)read [...]]]></description>
		<link>http://roy.gbiv.com/untangled/2008/information-networks</link>
			</item>
	<item>
		<title>On software architecture</title>
		<description><![CDATA[I ran across a spout yesterday about the uniform interface in REST. Actually, it is more of an attack on resource-oriented architecture (ROA) with the usual sideswipes at REST. Like most criticisms of my work, it got me thinking&#8230; not just about what was being criticized (in this case, the lack of REST constraint enforcement [...]]]></description>
		<link>http://roy.gbiv.com/untangled/2008/on-software-architecture</link>
			</item>
</channel>
</rss>

<!-- Dynamic Page Served (once) in 0.422 seconds -->
