<?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: Pecia: Towards a Fluent Interface for Building Documents</title>
	<atom:link href="http://blog.xebia.com/2009/06/25/fluent-interface-for-documentation/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.xebia.com/2009/06/25/fluent-interface-for-documentation/</link>
	<description></description>
	<lastBuildDate>Thu, 11 Mar 2010 16:23:01 +0100</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.4</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Wilfred springer</title>
		<link>http://blog.xebia.com/2009/06/25/fluent-interface-for-documentation/comment-page-1/#comment-92372</link>
		<dc:creator>Wilfred springer</dc:creator>
		<pubDate>Sun, 30 Aug 2009 15:32:16 +0000</pubDate>
		<guid isPermaLink="false">http://blog.xebia.com/?p=2202#comment-92372</guid>
		<description>Hi Anthony,

Pecia does not return Strings; if you call .para() on an object, you cat a Para implementation upon which you can call other methods, for creating paragraph content. Those objects are basically shortly-living objects. In the current implementation of Pecia (found here: http://pecia.flotsam.nl/), data will be written to an StAX type of document writer as quickly as possible.</description>
		<content:encoded><![CDATA[<p>Hi Anthony,</p>
<p>Pecia does not return Strings; if you call .para() on an object, you cat a Para implementation upon which you can call other methods, for creating paragraph content. Those objects are basically shortly-living objects. In the current implementation of Pecia (found here: <a href="http://pecia.flotsam.nl/)" rel="nofollow">http://pecia.flotsam.nl/)</a>, data will be written to an StAX type of document writer as quickly as possible.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Anthony Gatlin</title>
		<link>http://blog.xebia.com/2009/06/25/fluent-interface-for-documentation/comment-page-1/#comment-92366</link>
		<dc:creator>Anthony Gatlin</dc:creator>
		<pubDate>Sat, 29 Aug 2009 07:44:56 +0000</pubDate>
		<guid isPermaLink="false">http://blog.xebia.com/?p=2202#comment-92366</guid>
		<description>I think this is a very interesting idea but there are a few wrinkles that must be considered. As you understand, the primary idea behind method chaining is that every method returns a type from which any available methods on that type can be called. If the output of every method was a string, this would cause incredible performance problems since strings are immutable and have to be recreated with each modification. However, if the methods which were called returned some implementation of something like StringBuilder, then the final document would not have to be rendered until it was complete. All of the method chaining could occur on the StringBuilder object or its derivatives. Your idea has great promise. I would be interested in discussing this idea further. Thanks for sharing it!</description>
		<content:encoded><![CDATA[<p>I think this is a very interesting idea but there are a few wrinkles that must be considered. As you understand, the primary idea behind method chaining is that every method returns a type from which any available methods on that type can be called. If the output of every method was a string, this would cause incredible performance problems since strings are immutable and have to be recreated with each modification. However, if the methods which were called returned some implementation of something like StringBuilder, then the final document would not have to be rendered until it was complete. All of the method chaining could occur on the StringBuilder object or its derivatives. Your idea has great promise. I would be interested in discussing this idea further. Thanks for sharing it!</p>
]]></content:encoded>
	</item>
</channel>
</rss>
