<?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: NHibernate 2nd level cache and multiple databases</title>
	<atom:link href="http://lostechies.com/gabrielschenker/2009/04/17/nhibernate-2nd-level-cache-and-multiple-databases/feed/" rel="self" type="application/rss+xml" />
	<link>http://lostechies.com/gabrielschenker/2009/04/17/nhibernate-2nd-level-cache-and-multiple-databases/</link>
	<description>Blog about architectural patterns, best practices, coding principles and techniques</description>
	<lastBuildDate>Tue, 02 Apr 2013 00:12:00 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.4.2</generator>
	<item>
		<title>By: Joe</title>
		<link>http://lostechies.com/gabrielschenker/2009/04/17/nhibernate-2nd-level-cache-and-multiple-databases/#comment-137</link>
		<dc:creator>Joe</dc:creator>
		<pubDate>Thu, 24 Feb 2011 12:40:33 +0000</pubDate>
		<guid isPermaLink="false">/blogs/gabrielschenker/archive/2009/04/17/nhibernate-2nd-level-cache-and-multiple-databases.aspx#comment-137</guid>
		<description>here is a good read about how a distributed cache can be used as NHinerbate L2 cache, 

http://www.alachisoft.com/ncache/nhibernate_l2cache_index.html</description>
		<content:encoded><![CDATA[<p>here is a good read about how a distributed cache can be used as NHinerbate L2 cache, </p>
<p><a href="http://www.alachisoft.com/ncache/nhibernate_l2cache_index.html" rel="nofollow">http://www.alachisoft.com/ncache/nhibernate_l2cache_index.html</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: jerry</title>
		<link>http://lostechies.com/gabrielschenker/2009/04/17/nhibernate-2nd-level-cache-and-multiple-databases/#comment-136</link>
		<dc:creator>jerry</dc:creator>
		<pubDate>Tue, 08 Feb 2011 11:33:51 +0000</pubDate>
		<guid isPermaLink="false">/blogs/gabrielschenker/archive/2009/04/17/nhibernate-2nd-level-cache-and-multiple-databases.aspx#comment-136</guid>
		<description>all have written the same. write something for beginers.</description>
		<content:encoded><![CDATA[<p>all have written the same. write something for beginers.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Steve</title>
		<link>http://lostechies.com/gabrielschenker/2009/04/17/nhibernate-2nd-level-cache-and-multiple-databases/#comment-135</link>
		<dc:creator>Steve</dc:creator>
		<pubDate>Thu, 29 Apr 2010 11:54:17 +0000</pubDate>
		<guid isPermaLink="false">/blogs/gabrielschenker/archive/2009/04/17/nhibernate-2nd-level-cache-and-multiple-databases.aspx#comment-135</guid>
		<description>NHibernate is very famous among the developer’s community as it has a lot of advantages for them. But it cannot handle ASP.NET worker process recycling. So the use of cache providers like NCache or Velocity can be a good option. NCache acts like a second level distributed cache which can enhance the performance of the app. 	</description>
		<content:encoded><![CDATA[<p>NHibernate is very famous among the developer’s community as it has a lot of advantages for them. But it cannot handle ASP.NET worker process recycling. So the use of cache providers like NCache or Velocity can be a good option. NCache acts like a second level distributed cache which can enhance the performance of the app. 	</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Gabriel N. Schenker</title>
		<link>http://lostechies.com/gabrielschenker/2009/04/17/nhibernate-2nd-level-cache-and-multiple-databases/#comment-134</link>
		<dc:creator>Gabriel N. Schenker</dc:creator>
		<pubDate>Fri, 17 Apr 2009 17:56:32 +0000</pubDate>
		<guid isPermaLink="false">/blogs/gabrielschenker/archive/2009/04/17/nhibernate-2nd-level-cache-and-multiple-databases.aspx#comment-134</guid>
		<description>@DaRaga: that&#039;s what I was expecting too, that the cache provider should automatically detect that it is called from 2 different session factories. Maybe I should test the other providers too and compare their behavior...</description>
		<content:encoded><![CDATA[<p>@DaRaga: that&#8217;s what I was expecting too, that the cache provider should automatically detect that it is called from 2 different session factories. Maybe I should test the other providers too and compare their behavior&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: DaRage</title>
		<link>http://lostechies.com/gabrielschenker/2009/04/17/nhibernate-2nd-level-cache-and-multiple-databases/#comment-133</link>
		<dc:creator>DaRage</dc:creator>
		<pubDate>Fri, 17 Apr 2009 13:20:26 +0000</pubDate>
		<guid isPermaLink="false">/blogs/gabrielschenker/archive/2009/04/17/nhibernate-2nd-level-cache-and-multiple-databases.aspx#comment-133</guid>
		<description>This is clearly a bug and not a configuration issue. This configuration parameter should not have been exposed in the first place and it is the session factory responsibility to guarantee independence from other session factories. after that is done then you can implement a feature that make 2 session factories use the same cache just like you have 2 applications with the same encryption keys. but that&#039;s another story. The default behavior should differentiate between session factories. This definitely needs to be submitted as an issue.

</description>
		<content:encoded><![CDATA[<p>This is clearly a bug and not a configuration issue. This configuration parameter should not have been exposed in the first place and it is the session factory responsibility to guarantee independence from other session factories. after that is done then you can implement a feature that make 2 session factories use the same cache just like you have 2 applications with the same encryption keys. but that&#8217;s another story. The default behavior should differentiate between session factories. This definitely needs to be submitted as an issue.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
