<?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: Parsing Email Date Formats</title>
	<atom:link href="http://outerlevel.com/blog/2007/06/22/parsing-email-date-formats/feed/" rel="self" type="application/rss+xml" />
	<link>http://outerlevel.com/blog/2007/06/22/parsing-email-date-formats/</link>
	<description>Building a MicroISV</description>
	<pubDate>Tue, 06 Jan 2009 06:11:38 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.6.5</generator>
		<item>
		<title>By: Jon Trainer</title>
		<link>http://outerlevel.com/blog/2007/06/22/parsing-email-date-formats/#comment-934</link>
		<dc:creator>Jon Trainer</dc:creator>
		<pubDate>Fri, 22 Jun 2007 16:35:06 +0000</pubDate>
		<guid isPermaLink="false">http://outerlevel.com/blog/2007/06/22/parsing-email-date-formats/#comment-934</guid>
		<description>I've been making more and more use of this pattern lately.   Supporting multiple external systems that have similar behavior but slightly different formats lends itself nicely to this approach.</description>
		<content:encoded><![CDATA[<p>I&#8217;ve been making more and more use of this pattern lately.   Supporting multiple external systems that have similar behavior but slightly different formats lends itself nicely to this approach.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Daniel Jalkut</title>
		<link>http://outerlevel.com/blog/2007/06/22/parsing-email-date-formats/#comment-933</link>
		<dc:creator>Daniel Jalkut</dc:creator>
		<pubDate>Fri, 22 Jun 2007 16:21:09 +0000</pubDate>
		<guid isPermaLink="false">http://outerlevel.com/blog/2007/06/22/parsing-email-date-formats/#comment-933</guid>
		<description>Cool move. I ran into a similar problem with MarsEdit, which of course has to make sense of the date strings that come along with downloaded blog posts from various systems. At some point one of the systems changed its format subtly and I had to add another case as you have done. 

It would be a great idea for me to follow your lead and put them in an editable resource. A really nice side-effect of doing this is that you can prescribe an "emergency fix" for power users to apply without requiring an update of the code.</description>
		<content:encoded><![CDATA[<p>Cool move. I ran into a similar problem with MarsEdit, which of course has to make sense of the date strings that come along with downloaded blog posts from various systems. At some point one of the systems changed its format subtly and I had to add another case as you have done. </p>
<p>It would be a great idea for me to follow your lead and put them in an editable resource. A really nice side-effect of doing this is that you can prescribe an &#8220;emergency fix&#8221; for power users to apply without requiring an update of the code.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
