<?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: Maintaining State in Reporting Services 2008	</title>
	<atom:link href="https://prologika.com/maintaining-state-in-reporting-services-2008/feed/" rel="self" type="application/rss+xml" />
	<link>https://prologika.com/maintaining-state-in-reporting-services-2008/</link>
	<description>Business Intelligence Consulting and Training in Atlanta</description>
	<lastBuildDate>Wed, 17 Feb 2016 10:05:36 +0000</lastBuildDate>
	<sy:updatePeriod>
	hourly	</sy:updatePeriod>
	<sy:updateFrequency>
	1	</sy:updateFrequency>
	<generator>https://wordpress.org/?v=6.9.4</generator>
	<item>
		<title>
		By: ASP808		</title>
		<link>https://prologika.com/maintaining-state-in-reporting-services-2008/#comment-122</link>

		<dc:creator><![CDATA[ASP808]]></dc:creator>
		<pubDate>Tue, 22 Jun 2010 20:10:07 +0000</pubDate>
		<guid isPermaLink="false">/CS/blogs/blog/archive/2009/06/30/maintaining-state-in-reporting-services-2008.aspx#comment-122</guid>

					<description><![CDATA[Hi, need some further detail. 

What should the expression be for the text box that is storing the data? 
And what should the expression be for the text box that is retrieving the data? 
What is id and column ?
Where should the rest of the function be called? such as the onInit() OR is it called automatically on each render?]]></description>
			<content:encoded><![CDATA[<p>Hi, need some further detail. </p>
<p>What should the expression be for the text box that is storing the data?<br />
And what should the expression be for the text box that is retrieving the data?<br />
What is id and column ?<br />
Where should the rest of the function be called? such as the onInit() OR is it called automatically on each render?</p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		By: tlachev		</title>
		<link>https://prologika.com/maintaining-state-in-reporting-services-2008/#comment-121</link>

		<dc:creator><![CDATA[tlachev]]></dc:creator>
		<pubDate>Wed, 26 Aug 2009 11:51:15 +0000</pubDate>
		<guid isPermaLink="false">/CS/blogs/blog/archive/2009/06/30/maintaining-state-in-reporting-services-2008.aspx#comment-121</guid>

					<description><![CDATA[Nope, no such method]]></description>
			<content:encoded><![CDATA[<p>Nope, no such method</p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		By: joftingson		</title>
		<link>https://prologika.com/maintaining-state-in-reporting-services-2008/#comment-120</link>

		<dc:creator><![CDATA[joftingson]]></dc:creator>
		<pubDate>Wed, 26 Aug 2009 08:53:58 +0000</pubDate>
		<guid isPermaLink="false">/CS/blogs/blog/archive/2009/06/30/maintaining-state-in-reporting-services-2008.aspx#comment-120</guid>

					<description><![CDATA[Hi, 
Is there also a special method like On_Unload that can be used inside a custom code?

Thanks, 

Joefer]]></description>
			<content:encoded><![CDATA[<p>Hi,<br />
Is there also a special method like On_Unload that can be used inside a custom code?</p>
<p>Thanks, </p>
<p>Joefer</p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		By: tlachev		</title>
		<link>https://prologika.com/maintaining-state-in-reporting-services-2008/#comment-119</link>

		<dc:creator><![CDATA[tlachev]]></dc:creator>
		<pubDate>Thu, 02 Jul 2009 20:19:47 +0000</pubDate>
		<guid isPermaLink="false">/CS/blogs/blog/archive/2009/06/30/maintaining-state-in-reporting-services-2008.aspx#comment-119</guid>

					<description><![CDATA[Samsonfr,

Yes, it turns out that even if the hashtable key is user-specific and we do only adds and deletes (not updates to items from other users), we do need to make access to the hashtable collection thread-safe. I updated the blog. Thanks for pointing this out!]]></description>
			<content:encoded><![CDATA[<p>Samsonfr,</p>
<p>Yes, it turns out that even if the hashtable key is user-specific and we do only adds and deletes (not updates to items from other users), we do need to make access to the hashtable collection thread-safe. I updated the blog. Thanks for pointing this out!</p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		By: samsonfr		</title>
		<link>https://prologika.com/maintaining-state-in-reporting-services-2008/#comment-118</link>

		<dc:creator><![CDATA[samsonfr]]></dc:creator>
		<pubDate>Thu, 02 Jul 2009 17:13:31 +0000</pubDate>
		<guid isPermaLink="false">/CS/blogs/blog/archive/2009/06/30/maintaining-state-in-reporting-services-2008.aspx#comment-118</guid>

					<description><![CDATA[Thanks for sharing this with us. I was not aware of the multi-paging behavior.

Shouldn&#039;t you protect yourself against multithreaded issues? Multiple threads can access your static hashtable at the same time, shouldn&#039;t you use locks?]]></description>
			<content:encoded><![CDATA[<p>Thanks for sharing this with us. I was not aware of the multi-paging behavior.</p>
<p>Shouldn&#8217;t you protect yourself against multithreaded issues? Multiple threads can access your static hashtable at the same time, shouldn&#8217;t you use locks?</p>
]]></content:encoded>
		
			</item>
	</channel>
</rss>
