<?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: Agatha Feature Suggestion: Caching</title>
	<atom:link href="http://davybrion.com/blog/2009/12/agatha-feature-suggestion-caching/feed/" rel="self" type="application/rss+xml" />
	<link>http://davybrion.com/blog/2009/12/agatha-feature-suggestion-caching/</link>
	<description>Trying to walk that thin line between intelligence and ignorance</description>
	<lastBuildDate>Thu, 09 Sep 2010 13:37:05 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0.1</generator>
	<item>
		<title>By: Britney</title>
		<link>http://davybrion.com/blog/2009/12/agatha-feature-suggestion-caching/comment-page-1/#comment-33439</link>
		<dc:creator>Britney</dc:creator>
		<pubDate>Wed, 24 Mar 2010 12:45:41 +0000</pubDate>
		<guid isPermaLink="false">http://davybrion.com/blog/2009/12/agatha-feature-suggestion-caching/#comment-33439</guid>
		<description>Looks like a good idea! But will it work in a practical environment …………. The main advantage of using NHibernate over this sort of caching is that NHibernate has some proven result. There are some cache providers which offer support for second level caching and &lt;a href=&quot;http://www.alachisoft.com/ncache/index.html&quot; rel=&quot;nofollow&quot;&gt;NCache&lt;/a&gt;being the most famous one.</description>
		<content:encoded><![CDATA[<p>Looks like a good idea! But will it work in a practical environment …………. The main advantage of using NHibernate over this sort of caching is that NHibernate has some proven result. There are some cache providers which offer support for second level caching and <a href="http://www.alachisoft.com/ncache/index.html" rel="nofollow">NCache</a>being the most famous one.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Reflective Perspective - Chris Alcock &#187; The Morning Brew #497</title>
		<link>http://davybrion.com/blog/2009/12/agatha-feature-suggestion-caching/comment-page-1/#comment-23203</link>
		<dc:creator>Reflective Perspective - Chris Alcock &#187; The Morning Brew #497</dc:creator>
		<pubDate>Mon, 14 Dec 2009 09:41:04 +0000</pubDate>
		<guid isPermaLink="false">http://davybrion.com/blog/2009/12/agatha-feature-suggestion-caching/#comment-23203</guid>
		<description>[...] Agatha Feature Suggestion: Caching - Davy Brion starts investigating response caching capabilities for his Agatha Service Layer Implementation and already has a post&#8217;Agatha&#8217;s Caching Layer Implementation: First Draft&#8216; providing the first draft (in code) of such a feature [...]</description>
		<content:encoded><![CDATA[<p>[...] Agatha Feature Suggestion: Caching &#8211; Davy Brion starts investigating response caching capabilities for his Agatha Service Layer Implementation and already has a post&#8217;Agatha&#8217;s Caching Layer Implementation: First Draft&#8216; providing the first draft (in code) of such a feature [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Davy Brion</title>
		<link>http://davybrion.com/blog/2009/12/agatha-feature-suggestion-caching/comment-page-1/#comment-23194</link>
		<dc:creator>Davy Brion</dc:creator>
		<pubDate>Sun, 13 Dec 2009 13:38:06 +0000</pubDate>
		<guid isPermaLink="false">http://davybrion.com/blog/2009/12/agatha-feature-suggestion-caching/#comment-23194</guid>
		<description>@TomC

yeah that has crossed my mind but then there would be no way to invalidate client-side cached responses

(yes, you could do it with wcf duplex channels but that would be wcf specific which i want to avoid)</description>
		<content:encoded><![CDATA[<p>@TomC</p>
<p>yeah that has crossed my mind but then there would be no way to invalidate client-side cached responses</p>
<p>(yes, you could do it with wcf duplex channels but that would be wcf specific which i want to avoid)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: TomC</title>
		<link>http://davybrion.com/blog/2009/12/agatha-feature-suggestion-caching/comment-page-1/#comment-23193</link>
		<dc:creator>TomC</dc:creator>
		<pubDate>Sun, 13 Dec 2009 13:33:27 +0000</pubDate>
		<guid isPermaLink="false">http://davybrion.com/blog/2009/12/agatha-feature-suggestion-caching/#comment-23193</guid>
		<description>I assume that the caching is completely server-side, as it would be the most logical place to invalidate cache regions etc., but would it also be useful to have some kind of client-side caching? The main advantage of client-side caching would be to reduce remote calls (via WCF or something else), but can get pretty complex while batching requests.
Any thoughts on this? (I&#039;m just thinking out loud here...)</description>
		<content:encoded><![CDATA[<p>I assume that the caching is completely server-side, as it would be the most logical place to invalidate cache regions etc., but would it also be useful to have some kind of client-side caching? The main advantage of client-side caching would be to reduce remote calls (via WCF or something else), but can get pretty complex while batching requests.<br />
Any thoughts on this? (I&#8217;m just thinking out loud here&#8230;)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Davy Brion</title>
		<link>http://davybrion.com/blog/2009/12/agatha-feature-suggestion-caching/comment-page-1/#comment-23192</link>
		<dc:creator>Davy Brion</dc:creator>
		<pubDate>Sun, 13 Dec 2009 11:35:17 +0000</pubDate>
		<guid isPermaLink="false">http://davybrion.com/blog/2009/12/agatha-feature-suggestion-caching/#comment-23192</guid>
		<description>@Ayende

i know, but i don&#039;t think that&#039;s possible for this kind of caching... having to handle it explicitly in some cases probably won&#039;t be an issue for most people i think.</description>
		<content:encoded><![CDATA[<p>@Ayende</p>
<p>i know, but i don&#8217;t think that&#8217;s possible for this kind of caching&#8230; having to handle it explicitly in some cases probably won&#8217;t be an issue for most people i think.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ayende Rahien</title>
		<link>http://davybrion.com/blog/2009/12/agatha-feature-suggestion-caching/comment-page-1/#comment-23190</link>
		<dc:creator>Ayende Rahien</dc:creator>
		<pubDate>Sun, 13 Dec 2009 01:54:14 +0000</pubDate>
		<guid isPermaLink="false">http://davybrion.com/blog/2009/12/agatha-feature-suggestion-caching/#comment-23190</guid>
		<description>Davy,
One of the things that makes NH caching works really well is that it understand when to handle expiry based on the tables involved in a query.
That is a hugely important issue for caching, because it means you don&#039;t have to explicitly handles this.</description>
		<content:encoded><![CDATA[<p>Davy,<br />
One of the things that makes NH caching works really well is that it understand when to handle expiry based on the tables involved in a query.<br />
That is a hugely important issue for caching, because it means you don&#8217;t have to explicitly handles this.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: VirtualStaticVoid</title>
		<link>http://davybrion.com/blog/2009/12/agatha-feature-suggestion-caching/comment-page-1/#comment-23188</link>
		<dc:creator>VirtualStaticVoid</dc:creator>
		<pubDate>Sat, 12 Dec 2009 18:06:02 +0000</pubDate>
		<guid isPermaLink="false">http://davybrion.com/blog/2009/12/agatha-feature-suggestion-caching/#comment-23188</guid>
		<description>Perhaps the request/response classes which are deterministic could be decorated with an attribute to indicate this. In this way, the service handling the request can return the cached response for subsequent requests. There could also be additional meta associated which specifies lifetime behavior for the cached responses.</description>
		<content:encoded><![CDATA[<p>Perhaps the request/response classes which are deterministic could be decorated with an attribute to indicate this. In this way, the service handling the request can return the cached response for subsequent requests. There could also be additional meta associated which specifies lifetime behavior for the cached responses.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Deathraven</title>
		<link>http://davybrion.com/blog/2009/12/agatha-feature-suggestion-caching/comment-page-1/#comment-23187</link>
		<dc:creator>Deathraven</dc:creator>
		<pubDate>Sat, 12 Dec 2009 17:48:13 +0000</pubDate>
		<guid isPermaLink="false">http://davybrion.com/blog/2009/12/agatha-feature-suggestion-caching/#comment-23187</guid>
		<description>I think its an overall solid idea :). And I agree that using Attributes would provide the best solution.</description>
		<content:encoded><![CDATA[<p>I think its an overall solid idea <img src='http://davybrion.com/blog/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /> . And I agree that using Attributes would provide the best solution.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

<!-- Dynamic page generated in 0.267 seconds. -->
<!-- Cached page generated by WP-Super-Cache on 2010-09-09 17:32:42 -->
