<?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: Real-time web for retailers</title>
	<atom:link href="http://blog.prwd.co.uk/technology/real-time-web-for-retailers/feed" rel="self" type="application/rss+xml" />
	<link>http://blog.prwd.co.uk/uncategorized/real-time-web-for-retailers</link>
	<description>Experts in usability, e-commerce and web development</description>
	<lastBuildDate>Fri, 16 Dec 2011 20:17:19 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0.1</generator>
	<item>
		<title>By: Rob Knight</title>
		<link>http://blog.prwd.co.uk/uncategorized/real-time-web-for-retailers/comment-page-1#comment-4</link>
		<dc:creator>Rob Knight</dc:creator>
		<pubDate>Thu, 14 May 2009 10:59:27 +0000</pubDate>
		<guid isPermaLink="false">http://blog.prwd.co.uk/?p=34#comment-4</guid>
		<description>XMPP isn&#039;t meant to replace HTTP completely, but it may be a better transport for real-time information in most cases.  It&#039;s worth remembering that XMPP can be proxied over a HTTP connection anyway - but this is getting into the kind of stuff I want to talk about in my next post!

I agree that the move to real-time is important, especially given that the web is currently not built for real-time communication at all.  It works best for mostly static content that doesn&#039;t change much, enabling caching technologies to do most of the work.  Real-time is a challenge because none of those technologies apply.</description>
		<content:encoded><![CDATA[<p>XMPP isn&#8217;t meant to replace HTTP completely, but it may be a better transport for real-time information in most cases.  It&#8217;s worth remembering that XMPP can be proxied over a HTTP connection anyway &#8211; but this is getting into the kind of stuff I want to talk about in my next post!</p>
<p>I agree that the move to real-time is important, especially given that the web is currently not built for real-time communication at all.  It works best for mostly static content that doesn&#8217;t change much, enabling caching technologies to do most of the work.  Real-time is a challenge because none of those technologies apply.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Gerson</title>
		<link>http://blog.prwd.co.uk/uncategorized/real-time-web-for-retailers/comment-page-1#comment-2</link>
		<dc:creator>Gerson</dc:creator>
		<pubDate>Wed, 13 May 2009 08:04:04 +0000</pubDate>
		<guid isPermaLink="false">http://blog.prwd.co.uk/?p=34#comment-2</guid>
		<description>Interesting article. I found this from a search for &quot;real time web&quot;
after reading this article: &lt;a href=&quot;http://www.readwriteweb.com/archives/introduction_to_the_real_time_web.php&quot; rel=&quot;nofollow&quot;&gt;Introduction to the Real Time Web&lt;/a&gt;, published yesterday also.
Many interesting companies and individuals are talking about this!
Will real time technologies like XMPP ever replace the traditional
HTTP-based web though? It&#039;s a big change from the old methods.</description>
		<content:encoded><![CDATA[<p>Interesting article. I found this from a search for &#8220;real time web&#8221;<br />
after reading this article: <a href="http://www.readwriteweb.com/archives/introduction_to_the_real_time_web.php" rel="nofollow">Introduction to the Real Time Web</a>, published yesterday also.<br />
Many interesting companies and individuals are talking about this!<br />
Will real time technologies like XMPP ever replace the traditional<br />
HTTP-based web though? It&#8217;s a big change from the old methods.</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! -->
