<?xml version="1.0" encoding="utf-8"?><!-- generator="wordpress/2.0.2" -->
<rss version="2.0" 
	xmlns:content="http://purl.org/rss/1.0/modules/content/">
<channel>
	<title>Comments on: Polling versus a Notification mechanism</title>
	<link>http://www.andrewsw.com/news/?p=629</link>
	<description>The Blog of Andrew - at AndrewSW.com</description>
	<pubDate>Wed, 22 May 2013 23:07:14 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.0.2</generator>

	<item>
		<title>by: Richard MacManus</title>
		<link>http://www.andrewsw.com/news/?p=629#comment-650</link>
		<pubDate>Thu, 20 May 2004 03:12:19 +0000</pubDate>
		<guid>http://www.andrewsw.com/news/?p=629#comment-650</guid>
					<description>Thanks, interesting thoughts. In the case of Topics Aggregators, my case for polling was exclusively based on moving the requirement to ping/notify *away* from the user. That is, make the Aggregator do the work - which means polling. I've since discovered that K-Collector already does this (the pinging is a nice-to-have, but not absolutely necessary as KC will eventually poll it).</description>
		<content:encoded><![CDATA[<p>Thanks, interesting thoughts. In the case of Topics Aggregators, my case for polling was exclusively based on moving the requirement to ping/notify *away* from the user. That is, make the Aggregator do the work - which means polling. I&#8217;ve since discovered that K-Collector already does this (the pinging is a nice-to-have, but not absolutely necessary as KC will eventually poll it).
</p>
]]></content:encoded>
				</item>
</channel>
</rss>
