<?xml version="1.0" encoding="utf-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	>
<channel>
	<title>Comments on: Sensitivity Training</title>
	<atom:link href="http://www.coxesroost.net/journal/2007/08/29/sensitivity-training/feed" rel="self" type="application/rss+xml" />
	<link>http://www.coxesroost.net/journal/2007/08/29/sensitivity-training</link>
	<description>Asking the Stupid Questions since 1971</description>
	<pubDate>Sat, 30 Aug 2008 04:36:52 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.6.1</generator>
		<item>
		<title>By: Will</title>
		<link>http://www.coxesroost.net/journal/2007/08/29/sensitivity-training#comment-30286</link>
		<dc:creator>Will</dc:creator>
		<pubDate>Wed, 12 Sep 2007 03:33:09 +0000</pubDate>
		<guid isPermaLink="false">http://www.coxesroost.net/journal/2007/08/29/sensitivity-training#comment-30286</guid>
		<description>The problem showed when IBM fixed the bug, which they didn't know they had, in a more recent release of the application server.</description>
		<content:encoded><![CDATA[<p>The problem showed when IBM fixed the bug, which they didn&#8217;t know they had, in a more recent release of the application server.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: David Nesting</title>
		<link>http://www.coxesroost.net/journal/2007/08/29/sensitivity-training#comment-30108</link>
		<dc:creator>David Nesting</dc:creator>
		<pubDate>Sun, 09 Sep 2007 02:18:59 +0000</pubDate>
		<guid isPermaLink="false">http://www.coxesroost.net/journal/2007/08/29/sensitivity-training#comment-30108</guid>
		<description>Perhaps equally alarming is the HTTP 200 response code.  You can't get all mad at the user agents when the server-side application doesn't care either.  Many web application environments don't care at all what HTTP method is used.  Nevermind case.  When application servers try to map HTTP requests to application code, that map should use both method and path as the key, not path alone.</description>
		<content:encoded><![CDATA[<p>Perhaps equally alarming is the HTTP 200 response code.  You can&#8217;t get all mad at the user agents when the server-side application doesn&#8217;t care either.  Many web application environments don&#8217;t care at all what HTTP method is used.  Nevermind case.  When application servers try to map HTTP requests to application code, that map should use both method and path as the key, not path alone.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
