<?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: ASP.NET MVC Tip: Got an Ajax Request?</title>
	<atom:link href="http://www.minddriven.de/index.php/technology/dot-net/web/asp-net-mvc/aspnet-mvc-tipp-1-ajax-request/feed" rel="self" type="application/rss+xml" />
	<link>http://www.minddriven.de/index.php/technology/dot-net/web/asp-net-mvc/aspnet-mvc-tipp-1-ajax-request</link>
	<description>Matthias Jauernig -- .NET technology, architecture and design</description>
	<lastBuildDate>Thu, 02 Feb 2012 06:42:23 +0100</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.1</generator>
	<item>
		<title>By: ajdotnet</title>
		<link>http://www.minddriven.de/index.php/technology/dot-net/web/asp-net-mvc/aspnet-mvc-tipp-1-ajax-request/comment-page-1#comment-18</link>
		<dc:creator>ajdotnet</dc:creator>
		<pubDate>Thu, 04 Dec 2008 08:19:19 +0000</pubDate>
		<guid isPermaLink="false">http://www.leading-edge-dev.de/?p=78#comment-18</guid>
		<description>Nice post. Personally I do like the attribute version better because it clearly states the intention rather than polluting the code with the implementation. 
Also I&#039;d like to point out that arguing that either solution introduces view related logic into the controller is a valid point; however it is the sad truth (IMHO) that this will at one point happen anyway. Picking the view is the first &quot;fall of man&quot;, picking the data to be presented (which may be as view specific as it comes) follows shortly thereafter. Even the very functionality made available by the controller is at the end view specific, for it reflects the capability of the UI technology.

PS: I happend to be the first one to kick you ;-)
PPS: And I took the liberty to add you to my blogroll.

You may invite me for a coffee (it&#039;s free anyway ;-))</description>
		<content:encoded><![CDATA[<p>Nice post. Personally I do like the attribute version better because it clearly states the intention rather than polluting the code with the implementation.<br />
Also I&#8217;d like to point out that arguing that either solution introduces view related logic into the controller is a valid point; however it is the sad truth (IMHO) that this will at one point happen anyway. Picking the view is the first &#8220;fall of man&#8221;, picking the data to be presented (which may be as view specific as it comes) follows shortly thereafter. Even the very functionality made available by the controller is at the end view specific, for it reflects the capability of the UI technology.</p>
<p>PS: I happend to be the first one to kick you <img src='http://www.minddriven.de/wp-includes/images/smilies/icon_wink.gif' alt=';-)' class='wp-smiley' /><br />
PPS: And I took the liberty to add you to my blogroll.</p>
<p>You may invite me for a coffee (it&#8217;s free anyway <img src='http://www.minddriven.de/wp-includes/images/smilies/icon_wink.gif' alt=';-)' class='wp-smiley' /> )</p>
]]></content:encoded>
	</item>
</channel>
</rss>

