<?xml version="1.0" encoding="UTF-8"?><!-- generator="wordpress/2.2.3" -->
<rss version="2.0" 
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	>
<channel>
	<title>Comments on: Linq to SQL with WCF in a Multi Tiered Action &#8211; Part 1</title>
	<link>http://www.sidarok.com/web/blog/content/2008/05/26/linq-to-sql-with-wcf-in-a-multi-tiered-action-part-1.html</link>
	<description>still believes in coding to make dreams come true</description>
	<pubDate>Thu, 20 Nov 2008 20:15:40 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.2.3</generator>

	<item>
		<title>By: Sidar Ok</title>
		<link>http://www.sidarok.com/web/blog/content/2008/05/26/linq-to-sql-with-wcf-in-a-multi-tiered-action-part-1.html#comment-139</link>
		<dc:creator>Sidar Ok</dc:creator>
		<pubDate>Tue, 27 May 2008 08:30:08 +0000</pubDate>
		<guid>http://www.sidarok.com/web/blog/content/2008/05/26/linq-to-sql-with-wcf-in-a-multi-tiered-action-part-1.html#comment-139</guid>
		<description>Hi Javi, thanks for the nice thoughts. In the next post, I'll write the sample for data layer, and you are right, for select operations we are going to turn the Object Tracking off and it is more performant. But for Create, Update and Delete, since we need to call SubmitChanges in the context, Data Context can not be turned into readonly mode, otherwise it will throw InvalidOperationException - InvalidOperationException ObjectTrackingRequired. 

But as you said, when the data is read only, such as in Get operations, there is no need to turn object tracking on and there will be a significant performance increase in that.</description>
		<content:encoded><![CDATA[<p>Hi Javi, thanks for the nice thoughts. In the next post, I&#8217;ll write the sample for data layer, and you are right, for select operations we are going to turn the Object Tracking off and it is more performant. But for Create, Update and Delete, since we need to call SubmitChanges in the context, Data Context can not be turned into readonly mode, otherwise it will throw InvalidOperationException - InvalidOperationException ObjectTrackingRequired. </p>
<p>But as you said, when the data is read only, such as in Get operations, there is no need to turn object tracking on and there will be a significant performance increase in that.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Javier Crespo</title>
		<link>http://www.sidarok.com/web/blog/content/2008/05/26/linq-to-sql-with-wcf-in-a-multi-tiered-action-part-1.html#comment-138</link>
		<dc:creator>Javier Crespo</dc:creator>
		<pubDate>Tue, 27 May 2008 07:17:53 +0000</pubDate>
		<guid>http://www.sidarok.com/web/blog/content/2008/05/26/linq-to-sql-with-wcf-in-a-multi-tiered-action-part-1.html#comment-138</guid>
		<description>Great walkthrough, I've seen other posts about linqtosql and they mainly focus in a 1 layer application so I really appreciate a sample that fits the Application design/architecture requirements that I'm usually exposed to. 
I'm looking forward to the second part. 
A question for you: Would it be good performance wise to turn off ObjectTracking for this scenario where the DataContext is not kept alive beyond the DataAccess layer?</description>
		<content:encoded><![CDATA[<p>Great walkthrough, I&#8217;ve seen other posts about linqtosql and they mainly focus in a 1 layer application so I really appreciate a sample that fits the Application design/architecture requirements that I&#8217;m usually exposed to.<br />
I&#8217;m looking forward to the second part.<br />
A question for you: Would it be good performance wise to turn off ObjectTracking for this scenario where the DataContext is not kept alive beyond the DataAccess layer?</p>
]]></content:encoded>
	</item>
</channel>
</rss>
