<?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"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: STOMP Clarification</title>
	<atom:link href="http://hiramchirino.com/blog/2009/09/stomp-clarification/feed/" rel="self" type="application/rss+xml" />
	<link>http://hiramchirino.com/blog/2009/09/stomp-clarification/</link>
	<description>My Ramblings on Hawt Tech</description>
	<lastBuildDate>Fri, 20 Aug 2010 17:57:58 -0600</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.6</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: benjaminws</title>
		<link>http://hiramchirino.com/blog/2009/09/stomp-clarification/comment-page-1/#comment-37</link>
		<dc:creator>benjaminws</dc:creator>
		<pubDate>Mon, 21 Sep 2009 14:24:02 +0000</pubDate>
		<guid isPermaLink="false">http://hiramchirino.com/wordpress/2009/09/stomp-clarification/#comment-37</guid>
		<description>I&#039;ll agree with your statement about the newline after the terminator being natural.  I assumed that because the newline wasn&#039;t specified in the protocol, that it wasn&#039;t supposed to be there.&lt;br /&gt;&lt;br /&gt;In all honesty, this is such a small problem, that it didn&#039;t bother me that much to just account for both cases in code.&lt;br /&gt;&lt;br /&gt;It would be really nice if every implementation followed the spec to the letter, but even if it were more finely grained in detail, it probably wouldn&#039;t happen.&lt;br /&gt;&lt;br /&gt;I like your description and think it would be helpful to add that to the documentation.</description>
		<content:encoded><![CDATA[<p>I&#39;ll agree with your statement about the newline after the terminator being natural.  I assumed that because the newline wasn&#39;t specified in the protocol, that it wasn&#39;t supposed to be there.</p>
<p>In all honesty, this is such a small problem, that it didn&#39;t bother me that much to just account for both cases in code.</p>
<p>It would be really nice if every implementation followed the spec to the letter, but even if it were more finely grained in detail, it probably wouldn&#39;t happen.</p>
<p>I like your description and think it would be helpful to add that to the documentation.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
