<?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: Mark&#8217;s rebuttal on compensations with REST and JBPM</title>
	<atom:link href="http://bill.burkecentral.com/2007/09/18/marks-rebuttal-on-compensations-with-rest-and-jbpm/feed/" rel="self" type="application/rss+xml" />
	<link>http://bill.burkecentral.com/2007/09/18/marks-rebuttal-on-compensations-with-rest-and-jbpm/</link>
	<description>Middleware tech talk</description>
	<pubDate>Fri, 21 Nov 2008 23:09:40 +0000</pubDate>
	<generator>http://wordpress.org/?v=MU</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Andy</title>
		<link>http://bill.burkecentral.com/2007/09/18/marks-rebuttal-on-compensations-with-rest-and-jbpm/#comment-295</link>
		<dc:creator>Andy</dc:creator>
		<pubDate>Thu, 27 Sep 2007 01:43:46 +0000</pubDate>
		<guid isPermaLink="false">http://bill.burkecentral.com/2007/09/18/marks-rebuttal-on-compensations-with-rest-and-jbpm/#comment-295</guid>
		<description>I use whatever transport requires me to do the least amount of work and does not hamper performance.  For email the objects are simple, the data is big, I use XML because the platform has direct support for it and I have to do little if anything.  If I were passing a lot of small objects, tree structures and using a JIT, I'd use something like JSON or preserialized objects.  If it feels good do it.  If it hurts don't do it.  Sucking up 20,000 WS specs to send an object across the net, transaction or not, hurts performance and development time.  Until I don't have to try real hard, forget it.</description>
		<content:encoded><![CDATA[<p>I use whatever transport requires me to do the least amount of work and does not hamper performance.  For email the objects are simple, the data is big, I use XML because the platform has direct support for it and I have to do little if anything.  If I were passing a lot of small objects, tree structures and using a JIT, I&#8217;d use something like JSON or preserialized objects.  If it feels good do it.  If it hurts don&#8217;t do it.  Sucking up 20,000 WS specs to send an object across the net, transaction or not, hurts performance and development time.  Until I don&#8217;t have to try real hard, forget it.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: dbrum</title>
		<link>http://bill.burkecentral.com/2007/09/18/marks-rebuttal-on-compensations-with-rest-and-jbpm/#comment-232</link>
		<dc:creator>dbrum</dc:creator>
		<pubDate>Wed, 19 Sep 2007 14:33:21 +0000</pubDate>
		<guid isPermaLink="false">http://bill.burkecentral.com/2007/09/18/marks-rebuttal-on-compensations-with-rest-and-jbpm/#comment-232</guid>
		<description>Bill, you might want to check out Dan Diephouse's blog on the same subject area: http://netzooid.com/blog/2007/08/19/ease-of-development-rest-vs-rpc/

Oh, and sorry about the Jays - they have no business playing baseball anymore ;-)</description>
		<content:encoded><![CDATA[<p>Bill, you might want to check out Dan Diephouse&#8217;s blog on the same subject area: <a href="http://netzooid.com/blog/2007/08/19/ease-of-development-rest-vs-rpc/" rel="nofollow">http://netzooid.com/blog/2007/08/19/ease-of-development-rest-vs-rpc/</a></p>
<p>Oh, and sorry about the Jays - they have no business playing baseball anymore <img src='http://s.wordpress.com/wp-includes/images/smilies/icon_wink.gif' alt=';-)' class='wp-smiley' /> </p>
]]></content:encoded>
	</item>
</channel>
</rss>
