<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	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/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>willcodeforcoffee.com &#187; ASP.NET</title>
	<atom:link href="http://willcodeforcoffee.com/tag/aspnet/feed/" rel="self" type="application/rss+xml" />
	<link>http://willcodeforcoffee.com</link>
	<description>The personal programming blog of Eric Hoff.</description>
	<lastBuildDate>Tue, 02 Mar 2010 17:06:24 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0</generator>
		<item>
		<title>Those Dangerous UpdatePanels</title>
		<link>http://willcodeforcoffee.com/2008/09/23/those-dangerous-updatepanels/</link>
		<comments>http://willcodeforcoffee.com/2008/09/23/those-dangerous-updatepanels/#comments</comments>
		<pubDate>Tue, 23 Sep 2008 16:16:08 +0000</pubDate>
		<dc:creator>eric</dc:creator>
				<category><![CDATA[ASP.NET]]></category>

		<guid isPermaLink="false">http://willcodeforcoffee.com/?p=36</guid>
		<description><![CDATA[I&#8217;ve read the post from Encosia (Dave Ward) before, but I was reminded on the Twitter by MasterMaq about how dangerous UpdatePanels are a week or two ago. Okay, UpdatePanels aren&#8217;t dangerous, but they do use more bandwidth and server CPU than a simple web service call.  I figure a web developer ought to know [...]]]></description>
			<content:encoded><![CDATA[<p>I&#8217;ve read the post from <a href="http://encosia.com/" target="_blank">Encosia (Dave Ward)</a> before, but I was reminded on the Twitter by <a href="http://blog.mastermaq.ca/" target="_blank">MasterMaq</a> about how <a href="http://encosia.com/2007/07/11/why-aspnet-ajax-updatepanels-are-dangerous/" target="_self">dangerous UpdatePanels are</a> a week or two ago.</p>
<p>Okay, UpdatePanels aren&#8217;t <em>dangerous</em>, but they do use more bandwidth and server CPU than a simple web service call.  I figure a web developer ought to know what is being sent behind the scenes, but I can understand that a lot of people don&#8217;t.  UpdatePanels require sending the ViewState and building the control structure behind the scenes, as well as doing a subset of the ASP.NET Page event model, which means more data being POSTed behind the scenes and it takes a little longer to do all that processing.</p>
<p>UpdatePanels are easy though, and for some things in ASP.NET it is so much easier to use.  But Encosia does give us an <strong>awesome</strong> was to still use ASP.NET User Controls within web services and jQuery gives us some awesome tools to build pages dynamically without using UpdatePanels here: <a href="http://encosia.com/2008/02/05/boost-aspnet-performance-with-deferred-content-loading/" target="_blank">http://encosia.com/2008/02/05/boost-aspnet-performance-with-deferred-content-loading/</a>.  It&#8217;s not quite as easy to maintain as UpdatePanels, but it&#8217;s still <em>very</em> easy to use, and also very very fast.</p>
]]></content:encoded>
			<wfw:commentRss>http://willcodeforcoffee.com/2008/09/23/those-dangerous-updatepanels/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
	</channel>
</rss>
