<?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/"
	xmlns:itunes="http://www.itunes.com/dtds/podcast-1.0.dtd"
	xmlns:media="http://search.yahoo.com/mrss/"
	>
<channel>
	<title>Comments on: Delivery Status: Quickly Track Packages</title>
	<atom:link href="http://macapper.com/2007/06/27/delivery-status-quickly-track-packages/feed/" rel="self" type="application/rss+xml" />
	<link>http://macapper.com/2007/06/27/delivery-status-quickly-track-packages/</link>
	<description>Mac Apps, Reviews, Previews, Interviews, and Giveaways.</description>
	<lastBuildDate>Fri, 20 Nov 2009 15:57:29 -0800</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.5</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: wan acceleration</title>
		<link>http://macapper.com/2007/06/27/delivery-status-quickly-track-packages/comment-page-1/#comment-152888</link>
		<dc:creator>wan acceleration</dc:creator>
		<pubDate>Fri, 21 Nov 2008 09:14:43 +0000</pubDate>
		<guid isPermaLink="false">http://macapper.com/2007/06/27/delivery-status-quickly-track-packages/#comment-152888</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>
</channel>
</rss>
