<?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: On Distributed Applications</title>
	<atom:link href="http://averyblog.com/net/on-distributed-applications/feed/" rel="self" type="application/rss+xml" />
	<link>http://averyblog.com/net/on-distributed-applications/</link>
	<description>This is not the greatest tagline in the world... this is just a tribute.</description>
	<lastBuildDate>Mon, 11 Jan 2010 16:36:16 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.4</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: MikeWo</title>
		<link>http://averyblog.com/net/on-distributed-applications/comment-page-1/#comment-319</link>
		<dc:creator>MikeWo</dc:creator>
		<pubDate>Mon, 16 Feb 2004 10:50:00 +0000</pubDate>
		<guid isPermaLink="false">http://averyblog.infozerk.net/?p=98#comment-319</guid>
		<description>&lt;p&gt;I would have to agree with James on this.  Having recently left a company that provided these high-end, Enterprise level applications to customers to go to an internal position at a company that really doesn&#039;t need that level of application I can sympathize.  There were many times already where I have suggested what is probably an overkill solution to an issue.  Learning the real needs, as well as the most probable future needs, of an application should help determine if you need distributed logic in your apps.&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>I would have to agree with James on this.  Having recently left a company that provided these high-end, Enterprise level applications to customers to go to an internal position at a company that really doesn&#8217;t need that level of application I can sympathize.  There were many times already where I have suggested what is probably an overkill solution to an issue.  Learning the real needs, as well as the most probable future needs, of an application should help determine if you need distributed logic in your apps.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

