<?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: 3 Pitfalls to Avoid for a Faster Ektron CMS400 Website</title>
	<atom:link href="http://www.activoinc.com/blog/2008/03/17/3-pitfalls-to-avoid-for-a-faster-ektron-cms400-website/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.activoinc.com/blog/2008/03/17/3-pitfalls-to-avoid-for-a-faster-ektron-cms400-website/</link>
	<description>Web Development in a Web 2.0 World</description>
	<pubDate>Fri, 05 Dec 2008 00:24:31 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.6.5</generator>
		<item>
		<title>By: frankrusch</title>
		<link>http://www.activoinc.com/blog/2008/03/17/3-pitfalls-to-avoid-for-a-faster-ektron-cms400-website/#comment-960</link>
		<dc:creator>frankrusch</dc:creator>
		<pubDate>Wed, 04 Jun 2008 00:38:31 +0000</pubDate>
		<guid isPermaLink="false">http://www.activoinc.com/blog/2008/03/17/3-pitfalls-to-avoid-for-a-faster-ektron-cms400-website/#comment-960</guid>
		<description>Brian:
For reasonably complex sites, it's usually better to cache at the user control level, not the page level.

For example, a static page footer that's identical for all users, logged-in or not, can be aggressively cached. The footer could be written into an ascx user control that is shared across all instances.

On the other hand, a control that displays the current user name and login/logout link needs to be cached on a user-by-user basis:

For this situation, I've had good results using OutputCache and the VaryByCustom directive. In conjunction with VaryByCustom, override the GetVaryByCustomString() method in your Global.asax file and include logic to detect the current Ektron UserID. From there, a cache string can be constructed that is unique to each user.</description>
		<content:encoded><![CDATA[<p>Brian:<br />
For reasonably complex sites, it&#8217;s usually better to cache at the user control level, not the page level.</p>
<p>For example, a static page footer that&#8217;s identical for all users, logged-in or not, can be aggressively cached. The footer could be written into an ascx user control that is shared across all instances.</p>
<p>On the other hand, a control that displays the current user name and login/logout link needs to be cached on a user-by-user basis:</p>
<p>For this situation, I&#8217;ve had good results using OutputCache and the VaryByCustom directive. In conjunction with VaryByCustom, override the GetVaryByCustomString() method in your Global.asax file and include logic to detect the current Ektron UserID. From there, a cache string can be constructed that is unique to each user.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Brian</title>
		<link>http://www.activoinc.com/blog/2008/03/17/3-pitfalls-to-avoid-for-a-faster-ektron-cms400-website/#comment-959</link>
		<dc:creator>Brian</dc:creator>
		<pubDate>Fri, 16 May 2008 18:50:10 +0000</pubDate>
		<guid isPermaLink="false">http://www.activoinc.com/blog/2008/03/17/3-pitfalls-to-avoid-for-a-faster-ektron-cms400-website/#comment-959</guid>
		<description>Great article.  Could you give some ideas on what you have done for caching pages with logged in and anonymous users?  What did you vary on for Output caching.</description>
		<content:encoded><![CDATA[<p>Great article.  Could you give some ideas on what you have done for caching pages with logged in and anonymous users?  What did you vary on for Output caching.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
