<?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: Repository of Code</title>
	<atom:link href="http://www.computerjargon.com/2005/11/11/repository-of-code/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.computerjargon.com/2005/11/11/repository-of-code/</link>
	<description>The Life of Jason Motylinski</description>
	<pubDate>Tue, 06 Jan 2009 21:00:14 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.7</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: dick</title>
		<link>http://www.computerjargon.com/2005/11/11/repository-of-code/comment-page-1/#comment-54</link>
		<dc:creator>dick</dc:creator>
		<pubDate>Fri, 11 Nov 2005 13:09:08 +0000</pubDate>
		<guid isPermaLink="false">Repository of Code#comment-54</guid>
		<description>surprised to see the usage of the datatable vs the datareader for the binding of custom objects. a little caching object in there would be nice too. gotta make it scream. didn&#39;t know subversion could dump the source code like that, very cool.</description>
		<content:encoded><![CDATA[<p>surprised to see the usage of the datatable vs the datareader for the binding of custom objects. a little caching object in there would be nice too. gotta make it scream. didn&#39;t know subversion could dump the source code like that, very cool.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: jason</title>
		<link>http://www.computerjargon.com/2005/11/11/repository-of-code/comment-page-1/#comment-55</link>
		<dc:creator>jason</dc:creator>
		<pubDate>Fri, 11 Nov 2005 13:09:08 +0000</pubDate>
		<guid isPermaLink="false">Repository of Code#comment-55</guid>
		<description>You are right, there is definitely a strong argument for creating a data acess object layer, caching or otherwise, when dealing with MySQL. It&#39;s a pain in the rear dealing with inline SQL. At least when the database is MSSQL the stored procedures can aide in organizing standard data retrieval.</description>
		<content:encoded><![CDATA[<p>You are right, there is definitely a strong argument for creating a data acess object layer, caching or otherwise, when dealing with MySQL. It&#39;s a pain in the rear dealing with inline SQL. At least when the database is MSSQL the stored procedures can aide in organizing standard data retrieval.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
