<?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: Compressing Viewstate</title>
	<atom:link href="http://mikemason.ca/blog/2008/11/compressing-viewstate/feed/" rel="self" type="application/rss+xml" />
	<link>http://mikemason.ca/blog/2008/11/compressing-viewstate/</link>
	<description>agile thinking</description>
	<lastBuildDate>Mon, 28 Dec 2009 21:52:40 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: mike</title>
		<link>http://mikemason.ca/blog/2008/11/compressing-viewstate/comment-page-1/#comment-6457</link>
		<dc:creator>mike</dc:creator>
		<pubDate>Wed, 05 Nov 2008 16:22:25 +0000</pubDate>
		<guid isPermaLink="false">http://mikemason.ca/blog/?p=24#comment-6457</guid>
		<description>Typically we&#039;d see ViewState shrink from 200KB to maybe 15KB. On a small page you might see 15KB shrink to 4KB, so a 75% reduction. On some pages we&#039;d see even more impressive gains, up to 98%, but that usually indicated we were putting too much stuff into ViewState and should fix that before applying compression.

What&#039;s great about ViewState compression, as opposed to IIS page-level compression, is that the ViewState is compressed in both directions---when the user downloads the page and when they post back. Having a user submit a few hundred KB back to the server on each page request can really slow things down because typically home internet connections are optimized for downloads rather than uploads.</description>
		<content:encoded><![CDATA[<p>Typically we&#8217;d see ViewState shrink from 200KB to maybe 15KB. On a small page you might see 15KB shrink to 4KB, so a 75% reduction. On some pages we&#8217;d see even more impressive gains, up to 98%, but that usually indicated we were putting too much stuff into ViewState and should fix that before applying compression.</p>
<p>What&#8217;s great about ViewState compression, as opposed to IIS page-level compression, is that the ViewState is compressed in both directions&#8212;when the user downloads the page and when they post back. Having a user submit a few hundred KB back to the server on each page request can really slow things down because typically home internet connections are optimized for downloads rather than uploads.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Andreas Andreou</title>
		<link>http://mikemason.ca/blog/2008/11/compressing-viewstate/comment-page-1/#comment-6454</link>
		<dc:creator>Andreas Andreou</dc:creator>
		<pubDate>Wed, 05 Nov 2008 10:25:17 +0000</pubDate>
		<guid isPermaLink="false">http://mikemason.ca/blog/?p=24#comment-6454</guid>
		<description>You mention a 90% reduction in that case... What where the file sizes (in both the compressed and uncompressed versions) after gzip ?</description>
		<content:encoded><![CDATA[<p>You mention a 90% reduction in that case&#8230; What where the file sizes (in both the compressed and uncompressed versions) after gzip ?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Reflective Perspective - Chris Alcock &#187; The Morning Brew #216</title>
		<link>http://mikemason.ca/blog/2008/11/compressing-viewstate/comment-page-1/#comment-6452</link>
		<dc:creator>Reflective Perspective - Chris Alcock &#187; The Morning Brew #216</dc:creator>
		<pubDate>Wed, 05 Nov 2008 08:21:11 +0000</pubDate>
		<guid isPermaLink="false">http://mikemason.ca/blog/?p=24#comment-6452</guid>
		<description>[...] Compressing Viewstate - John Finlay looks at shrinking down the view state by compressing it, sharing code to do this and some real world examples of how its use vastly reduced the page size. [...]</description>
		<content:encoded><![CDATA[<p>[...] Compressing Viewstate &#8211; John Finlay looks at shrinking down the view state by compressing it, sharing code to do this and some real world examples of how its use vastly reduced the page size. [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>
