<?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: MS MVC: Routing - The Good, The Bad, The RESTful</title>
	<atom:link href="http://abombss.com/blog/2007/12/19/ms-mvc-routing-the-good-the-bad-the-restful/feed/" rel="self" type="application/rss+xml" />
	<link>http://abombss.com/blog/2007/12/19/ms-mvc-routing-the-good-the-bad-the-restful/</link>
	<description>Abstract &#38;&#38; Concrete</description>
	<pubDate>Tue, 06 Jan 2009 03:17:43 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.6.5</generator>
		<item>
		<title>By: Joe Ocampo</title>
		<link>http://abombss.com/blog/2007/12/19/ms-mvc-routing-the-good-the-bad-the-restful/#comment-20</link>
		<dc:creator>Joe Ocampo</dc:creator>
		<pubDate>Fri, 21 Dec 2007 21:55:38 +0000</pubDate>
		<guid isPermaLink="false">http://abombss.com/blog/2007/12/19/ms-mvc-routing-the-good-the-bad-the-restful/#comment-20</guid>
		<description>maybe not a new leaf but a small branch that listens to the community.. ;-)</description>
		<content:encoded><![CDATA[<p>maybe not a new leaf but a small branch that listens to the community.. <img src='http://abombss.com/wordpress/wp-includes/images/smilies/icon_wink.gif' alt=';-)' class='wp-smiley' /></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Adam Tybor</title>
		<link>http://abombss.com/blog/2007/12/19/ms-mvc-routing-the-good-the-bad-the-restful/#comment-19</link>
		<dc:creator>Adam Tybor</dc:creator>
		<pubDate>Thu, 20 Dec 2007 20:18:43 +0000</pubDate>
		<guid isPermaLink="false">http://abombss.com/blog/2007/12/19/ms-mvc-routing-the-good-the-bad-the-restful/#comment-19</guid>
		<description>No problem, I can't explain why I have been hung up on routing for so long now.  I think its been the discomfort in writing SEO friendly websites for clients in .Net.  It was just brutally difficult.

Right now I have all the confidence that Phil and team will take care of the majority of this stuff.... Weird, whens the last CTP Microsoft put out that you had confidence so many things could get changed.  

Is Microsoft turning over a new leaf?</description>
		<content:encoded><![CDATA[<p>No problem, I can&#8217;t explain why I have been hung up on routing for so long now.  I think its been the discomfort in writing SEO friendly websites for clients in .Net.  It was just brutally difficult.</p>
<p>Right now I have all the confidence that Phil and team will take care of the majority of this stuff&#8230;. Weird, whens the last CTP Microsoft put out that you had confidence so many things could get changed.  </p>
<p>Is Microsoft turning over a new leaf?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ben Scheirman</title>
		<link>http://abombss.com/blog/2007/12/19/ms-mvc-routing-the-good-the-bad-the-restful/#comment-15</link>
		<dc:creator>Ben Scheirman</dc:creator>
		<pubDate>Thu, 20 Dec 2007 16:59:43 +0000</pubDate>
		<guid isPermaLink="false">http://abombss.com/blog/2007/12/19/ms-mvc-routing-the-good-the-bad-the-restful/#comment-15</guid>
		<description>Just wanted to say thanks for your in-depth coverage.  It's definitely helpful.

Routes are one of the first areas you visit when evaluating the MVC framework and I share your sentiments that they need some powdered sugar or secret sauce to be more flexible.

Ultimately I think the MS MVC team will do whatever they can to correct some of these items.  Performance is probably the first one, as locking 20 times per request (for example) isn't going to cut it for most mid-size sites.</description>
		<content:encoded><![CDATA[<p>Just wanted to say thanks for your in-depth coverage.  It&#8217;s definitely helpful.</p>
<p>Routes are one of the first areas you visit when evaluating the MVC framework and I share your sentiments that they need some powdered sugar or secret sauce to be more flexible.</p>
<p>Ultimately I think the MS MVC team will do whatever they can to correct some of these items.  Performance is probably the first one, as locking 20 times per request (for example) isn&#8217;t going to cut it for most mid-size sites.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
