<?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 for Erata.NET</title>
	<atom:link href="http://www.erata.net/comments/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.erata.net</link>
	<description>If we don't have the solution you have the wrong problem</description>
	<lastBuildDate>Tue, 09 Mar 2010 15:34:36 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=abc</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>Comment on NServiceBus with NHibernate and MySQL by eti</title>
		<link>http://www.erata.net/net/nservicebus-with-nhibernate-and-mysql/comment-page-1/#comment-3708</link>
		<dc:creator>eti</dc:creator>
		<pubDate>Tue, 09 Mar 2010 15:34:36 +0000</pubDate>
		<guid isPermaLink="false">http://www.erata.net/net/nservicebus-with-nhibernate-and-mysql/#comment-3708</guid>
		<description>There is a bug on the MySQL connector&#039;s bug-tracker in witch the developers claim that before distributed transactions are supported by the connector they have to be supported by the server. If this is true and the MySQL server and native library don&#039;t support distributed transactions then i don&#039;t think ODBC can support it. And for unknown reasons i don&#039;t like ODBC :).

Anyway thanks for your suggestion.</description>
		<content:encoded><![CDATA[<p>There is a bug on the MySQL connector&#8217;s bug-tracker in witch the developers claim that before distributed transactions are supported by the connector they have to be supported by the server. If this is true and the MySQL server and native library don&#8217;t support distributed transactions then i don&#8217;t think ODBC can support it. And for unknown reasons i don&#8217;t like ODBC <img src='http://www.erata.net/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /> .</p>
<p>Anyway thanks for your suggestion.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on NServiceBus with NHibernate and MySQL by Jonathan</title>
		<link>http://www.erata.net/net/nservicebus-with-nhibernate-and-mysql/comment-page-1/#comment-3707</link>
		<dc:creator>Jonathan</dc:creator>
		<pubDate>Tue, 09 Mar 2010 12:42:27 +0000</pubDate>
		<guid isPermaLink="false">http://www.erata.net/net/nservicebus-with-nhibernate-and-mysql/#comment-3707</guid>
		<description>Although I haven&#039;t verified this, one possible option would be to use the MySQL ODBC connector instead of the .NET connector.  From what I understand it should support distributed transactions.</description>
		<content:encoded><![CDATA[<p>Although I haven&#8217;t verified this, one possible option would be to use the MySQL ODBC connector instead of the .NET connector.  From what I understand it should support distributed transactions.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Testing Windows Live Writer by technogran</title>
		<link>http://www.erata.net/news/testing-windows-live-writer/comment-page-1/#comment-3701</link>
		<dc:creator>technogran</dc:creator>
		<pubDate>Sat, 27 Feb 2010 19:01:34 +0000</pubDate>
		<guid isPermaLink="false">http://www.erata.net/news/testing-windows-live-writer/#comment-3701</guid>
		<description>Try taking a peak at my Blogging with Windows Live Writer posts for some how-to&#039;s and tips see http://technograns.wordpress.com</description>
		<content:encoded><![CDATA[<p>Try taking a peak at my Blogging with Windows Live Writer posts for some how-to&#8217;s and tips see <a href="http://technograns.wordpress.com" rel="nofollow">http://technograns.wordpress.com</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Qt4 Synchronous HTTP Request by eti</title>
		<link>http://www.erata.net/qt-boost/synchronous-http-request/comment-page-1/#comment-3700</link>
		<dc:creator>eti</dc:creator>
		<pubDate>Fri, 26 Feb 2010 11:50:46 +0000</pubDate>
		<guid isPermaLink="false">http://www.erata.net/weblog/qt-boost/2006/11/08/synchronous-http-request/#comment-3700</guid>
		<description>@Grzegorz 
It&#039;s been a while since I&#039;ve written this code, and at the moment i don&#039;t have access to a Qt installation so I&#039;m only guessing but:

I think that you can use the QHttp class to make more than one request at the same time, each having it&#039;s own request id and that&#039;s probably why trolltech designed the interface this way.

As for the &quot;bad&quot; responses i remember that i was curious about this at the time and that i discovered that the QHttp class can make other internal, protocol specific, requests witch are handled the same way as normal requests. I think that braking with a debugger when the &quot;bad&quot; response arrives will give you a clearer answer.</description>
		<content:encoded><![CDATA[<p>@Grzegorz<br />
It&#8217;s been a while since I&#8217;ve written this code, and at the moment i don&#8217;t have access to a Qt installation so I&#8217;m only guessing but:</p>
<p>I think that you can use the QHttp class to make more than one request at the same time, each having it&#8217;s own request id and that&#8217;s probably why trolltech designed the interface this way.</p>
<p>As for the &#8220;bad&#8221; responses i remember that i was curious about this at the time and that i discovered that the QHttp class can make other internal, protocol specific, requests witch are handled the same way as normal requests. I think that braking with a debugger when the &#8220;bad&#8221; response arrives will give you a clearer answer.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Qt4 Synchronous HTTP Request by Grzegorz.W</title>
		<link>http://www.erata.net/qt-boost/synchronous-http-request/comment-page-1/#comment-3699</link>
		<dc:creator>Grzegorz.W</dc:creator>
		<pubDate>Fri, 26 Feb 2010 08:58:07 +0000</pubDate>
		<guid isPermaLink="false">http://www.erata.net/weblog/qt-boost/2006/11/08/synchronous-http-request/#comment-3699</guid>
		<description>I have question about (IHMO) mysterious line that says
&#039;if(idx!=requestID) return;&#039;
How is it possible that the response could come with the Id other the was requested?
I&#039;m also using the syncHttp code and I&#039;ve noticed that when http request is done , it always assigns even number id&#039;s . &#039;requestFinished&#039; slot is fired twice, once for Id that is improper , and the second with one we want. 
Can anyone explain where do the &#039;bad&#039; reponses come from ?</description>
		<content:encoded><![CDATA[<p>I have question about (IHMO) mysterious line that says<br />
&#8216;if(idx!=requestID) return;&#8217;<br />
How is it possible that the response could come with the Id other the was requested?<br />
I&#8217;m also using the syncHttp code and I&#8217;ve noticed that when http request is done , it always assigns even number id&#8217;s . &#8216;requestFinished&#8217; slot is fired twice, once for Id that is improper , and the second with one we want.<br />
Can anyone explain where do the &#8216;bad&#8217; reponses come from ?</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on A few things from C++ that i miss in C# by eti</title>
		<link>http://www.erata.net/net/a-few-things-from-c-that-i-miss-in-c/comment-page-1/#comment-3692</link>
		<dc:creator>eti</dc:creator>
		<pubDate>Sun, 31 Jan 2010 07:42:26 +0000</pubDate>
		<guid isPermaLink="false">http://www.erata.net/?p=90#comment-3692</guid>
		<description>@Allon, thanks for your opinion on this. I have since than entered the world of NHibernate witch i can&#039;t say i fully know, but witch has proven to be pretty complex and feature-full ORM. I&#039;ve read about EF 4 and i&#039;m eager to play hoping that will be a log more than v3 was.</description>
		<content:encoded><![CDATA[<p>@Allon, thanks for your opinion on this. I have since than entered the world of NHibernate witch i can&#8217;t say i fully know, but witch has proven to be pretty complex and feature-full ORM. I&#8217;ve read about EF 4 and i&#8217;m eager to play hoping that will be a log more than v3 was.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on A few things from C++ that i miss in C# by Allon Guralnek</title>
		<link>http://www.erata.net/net/a-few-things-from-c-that-i-miss-in-c/comment-page-1/#comment-3690</link>
		<dc:creator>Allon Guralnek</dc:creator>
		<pubDate>Sat, 30 Jan 2010 17:15:39 +0000</pubDate>
		<guid isPermaLink="false">http://www.erata.net/?p=90#comment-3690</guid>
		<description>@eti, you should not use a long-living DataContext, ever! You might have a long-living IDbConnection, but beware that a DataContext can leak memory like crazy. A simple test would be to try and insert a million rows. You&#039;ll hit a OutOfMemoryException pretty fast, since the DataContext tried to track all the objects. The DataContext should be used on a per-operation basis, it&#039;s a lightweight object - create it and dispose of it at the end of a logical operation. Use the constructor that accepts a IDbConnection object to avoid connecting and disconnecting from the database with each operations.

In general, LINQ to SQL is a pretty basic and O/R Mapper, providing a very low level of abstraction. I suggest having a look at Entity Framework v4 which is included with .NET 4.0/VS2010 (EFv3, included with .NET3.5 SP1, what a bit... meh).</description>
		<content:encoded><![CDATA[<p>@eti, you should not use a long-living DataContext, ever! You might have a long-living IDbConnection, but beware that a DataContext can leak memory like crazy. A simple test would be to try and insert a million rows. You&#8217;ll hit a OutOfMemoryException pretty fast, since the DataContext tried to track all the objects. The DataContext should be used on a per-operation basis, it&#8217;s a lightweight object &#8211; create it and dispose of it at the end of a logical operation. Use the constructor that accepts a IDbConnection object to avoid connecting and disconnecting from the database with each operations.</p>
<p>In general, LINQ to SQL is a pretty basic and O/R Mapper, providing a very low level of abstraction. I suggest having a look at Entity Framework v4 which is included with .NET 4.0/VS2010 (EFv3, included with .NET3.5 SP1, what a bit&#8230; meh).</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Qt4 Synchronous HTTP Request by Yasir Hussain</title>
		<link>http://www.erata.net/qt-boost/synchronous-http-request/comment-page-1/#comment-3685</link>
		<dc:creator>Yasir Hussain</dc:creator>
		<pubDate>Sun, 17 Jan 2010 07:39:02 +0000</pubDate>
		<guid isPermaLink="false">http://www.erata.net/weblog/qt-boost/2006/11/08/synchronous-http-request/#comment-3685</guid>
		<description>Thank you very much for this Excellent piece of concept.</description>
		<content:encoded><![CDATA[<p>Thank you very much for this Excellent piece of concept.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Qt4 Synchronous HTTP Request by C# HTTP Request &#124; Erata.NET</title>
		<link>http://www.erata.net/qt-boost/synchronous-http-request/comment-page-1/#comment-3654</link>
		<dc:creator>C# HTTP Request &#124; Erata.NET</dc:creator>
		<pubDate>Sat, 21 Nov 2009 10:06:14 +0000</pubDate>
		<guid isPermaLink="false">http://www.erata.net/weblog/qt-boost/2006/11/08/synchronous-http-request/#comment-3654</guid>
		<description>[...] few years ago I’ve written an article on how to perform a synchronous HTTP request using Qt 4.2. I I’ve seen this article today and since now I’m mostly working [...]</description>
		<content:encoded><![CDATA[<p>[...] few years ago I’ve written an article on how to perform a synchronous HTTP request using Qt 4.2. I I’ve seen this article today and since now I’m mostly working [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on A few things from C++ that i miss in C# by eti</title>
		<link>http://www.erata.net/net/a-few-things-from-c-that-i-miss-in-c/comment-page-1/#comment-3651</link>
		<dc:creator>eti</dc:creator>
		<pubDate>Tue, 20 Oct 2009 09:06:24 +0000</pubDate>
		<guid isPermaLink="false">http://www.erata.net/?p=90#comment-3651</guid>
		<description>Hi all,
Funny thing that after this discussions i had an interesting debate at work. We are working with a DAL implemented using LINQ to SQL. Basically we have an MVC app that has Controllers witch use Services witch use Repositories witch use a LINQ DataContext. 

Now the DataContext generated by LINQ implements IDisposable, and when i see a class that implements IDisposable i want to play nice and dispose any instance created. The problem is that all the repositories share - for a request - the same DataContext instance and also the results of some linq queries are stored in cache so i can&#039;t really dispose of the DataContext at the end of the request since objects created by it might still exist in the cache and they hold a reference to the DataContext. 

Going deeper in the DataContext story I&#039;ve found out that you don&#039;t really have to dispose it since it will not keep the db connection open only the while executing the query and retrieving the results. So in the end the conclusion was that it&#039;s better, simpler to just leave it to the GC.

Still it feels strange to rely on the internal details of the DataContext ... but i guess it&#039;s one of the prices i have to pay for all the nice things that LINQ to SQL brings. 

@Ben: Man, i hear you on the non nullable types.</description>
		<content:encoded><![CDATA[<p>Hi all,<br />
Funny thing that after this discussions i had an interesting debate at work. We are working with a DAL implemented using LINQ to SQL. Basically we have an MVC app that has Controllers witch use Services witch use Repositories witch use a LINQ DataContext. </p>
<p>Now the DataContext generated by LINQ implements IDisposable, and when i see a class that implements IDisposable i want to play nice and dispose any instance created. The problem is that all the repositories share &#8211; for a request &#8211; the same DataContext instance and also the results of some linq queries are stored in cache so i can&#8217;t really dispose of the DataContext at the end of the request since objects created by it might still exist in the cache and they hold a reference to the DataContext. </p>
<p>Going deeper in the DataContext story I&#8217;ve found out that you don&#8217;t really have to dispose it since it will not keep the db connection open only the while executing the query and retrieving the results. So in the end the conclusion was that it&#8217;s better, simpler to just leave it to the GC.</p>
<p>Still it feels strange to rely on the internal details of the DataContext &#8230; but i guess it&#8217;s one of the prices i have to pay for all the nice things that LINQ to SQL brings. </p>
<p>@Ben: Man, i hear you on the non nullable types.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
