<?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: Using decision management to deliver intelligent business performance</title>
	<atom:link href="http://jtonedm.com/2008/08/05/using-decision-management-to-deliver-intelligent-business-performance/feed/" rel="self" type="application/rss+xml" />
	<link>http://jtonedm.com/2008/08/05/using-decision-management-to-deliver-intelligent-business-performance/</link>
	<description>James Taylor on Everything Decision Management</description>
	<lastBuildDate>Wed, 17 Mar 2010 09:47:49 -0700</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: wan acceleration technologies</title>
		<link>http://jtonedm.com/2008/08/05/using-decision-management-to-deliver-intelligent-business-performance/comment-page-1/#comment-11586</link>
		<dc:creator>wan acceleration technologies</dc:creator>
		<pubDate>Fri, 21 Nov 2008 00:09:46 +0000</pubDate>
		<guid isPermaLink="false">http://jtonedm.com/?p=528#comment-11586</guid>
		<description>John sums up telepresence from a network perspective, &quot;Telepresence is an interactive real- time application, which means it is delay sensitive, loss sensitive and jitter sensitive. This sounds familiar: it is just like VoIP, with the one difference being that it has huge bandwidth requirements.&quot; It&#039;s that last part that makes things more difficult. No form of QoS can allocate bandwidth that doesn&#039;t exist and it doesn&#039;t have provisions to force the application to downscale the experience based on realtime metrics. ...</description>
		<content:encoded><![CDATA[<p>John sums up telepresence from a network perspective, &#8220;Telepresence is an interactive real- time application, which means it is delay sensitive, loss sensitive and jitter sensitive. This sounds familiar: it is just like VoIP, with the one difference being that it has huge bandwidth requirements.&#8221; It&#8217;s that last part that makes things more difficult. No form of QoS can allocate bandwidth that doesn&#8217;t exist and it doesn&#8217;t have provisions to force the application to downscale the experience based on realtime metrics. &#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: The Secret Sauce is the Situation Models &#124; The Complex Event Processing Blog</title>
		<link>http://jtonedm.com/2008/08/05/using-decision-management-to-deliver-intelligent-business-performance/comment-page-1/#comment-10722</link>
		<dc:creator>The Secret Sauce is the Situation Models &#124; The Complex Event Processing Blog</dc:creator>
		<pubDate>Sat, 09 Aug 2008 10:23:26 +0000</pubDate>
		<guid isPermaLink="false">http://jtonedm.com/?p=528#comment-10722</guid>
		<description>[...] to business intelligence and business process management.   In turn, James Taylor  penned Using decision management to deliver intelligent business performance  where James rightly said that it does not require &#8220;heroic efforts&#8221; to integrate event [...]</description>
		<content:encoded><![CDATA[<p>[...] to business intelligence and business process management.   In turn, James Taylor  penned Using decision management to deliver intelligent business performance  where James rightly said that it does not require &#8220;heroic efforts&#8221; to integrate event [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>
<!-- WP Super Cache is installed but broken. The path to wp-cache-phase1.php in wp-content/advanced-cache.php must be fixed! -->