<?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"
	>
<channel>
	<title>Comments on: Using Value Objects in Fitnesse With Nested Tables</title>
	<atom:link href="http://blog.james-carr.org/2006/12/03/using-value-objects-in-fitnesse-with-nested-tables/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.james-carr.org/2006/12/03/using-value-objects-in-fitnesse-with-nested-tables/</link>
	<description>Rants and Musings of an Agile Developer</description>
	<pubDate>Sat, 22 Nov 2008 03:08:04 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.6.1</generator>
		<item>
		<title>By: Powers</title>
		<link>http://blog.james-carr.org/2006/12/03/using-value-objects-in-fitnesse-with-nested-tables/#comment-74623</link>
		<dc:creator>Powers</dc:creator>
		<pubDate>Thu, 19 Jun 2008 17:08:31 +0000</pubDate>
		<guid isPermaLink="false">http://blog.james-carr.org/?p=56#comment-74623</guid>
		<description>That is very cool!  Have you noticed whether there is a performance benefit to using inner_table defines vs defining tables in separate pages and using !include?

I say this because I have noticed that using too many !defines on a single page causes serious page load performance degradation in FitNesse.  !includes are expensive too, but I don't yet know which one is more costly.</description>
		<content:encoded><![CDATA[<p>That is very cool!  Have you noticed whether there is a performance benefit to using inner_table defines vs defining tables in separate pages and using !include?</p>
<p>I say this because I have noticed that using too many !defines on a single page causes serious page load performance degradation in FitNesse.  !includes are expensive too, but I don&#8217;t yet know which one is more costly.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
