<?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:georss="http://www.georss.org/georss" xmlns:geo="http://www.w3.org/2003/01/geo/wgs84_pos#" xmlns:media="http://search.yahoo.com/mrss/"
		>
<channel>
	<title>Comments on: Application Cache Refresh Call-back Trigger</title>
	<atom:link href="http://hicamel.wordpress.com/2007/06/05/application-cache-refresh-call-back-trigger/feed/" rel="self" type="application/rss+xml" />
	<link>http://hicamel.wordpress.com/2007/06/05/application-cache-refresh-call-back-trigger/</link>
	<description>SQL and PL/SQL code examples</description>
	<lastBuildDate>Wed, 14 Oct 2009 14:07:26 +0000</lastBuildDate>
	<generator>http://wordpress.com/</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Michael Moore</title>
		<link>http://hicamel.wordpress.com/2007/06/05/application-cache-refresh-call-back-trigger/#comment-56</link>
		<dc:creator>Michael Moore</dc:creator>
		<pubDate>Fri, 15 Jun 2007 16:57:58 +0000</pubDate>
		<guid isPermaLink="false">http://hicamel.wordpress.com/2007/06/05/application-cache-refresh-call-back-trigger/#comment-56</guid>
		<description>Yeah, but what are the odd that all of the servers are going to be down? In my case, it&#039;s very unlikely. Also, I would expect and average of 1 callback per minute, based  on what I know about our system. But your point is well taken. Personally, the most I&#039;d wait is 2 seconds: thinking that if I don&#039;t get a response after 2 seconds, it&#039;s not going to happen. If a person was really concerned about performance then this would not be a good solution. Probably they would want to use dbms_jobs. What would you do?
Regards,
Mike</description>
		<content:encoded><![CDATA[<p>Yeah, but what are the odd that all of the servers are going to be down? In my case, it&#8217;s very unlikely. Also, I would expect and average of 1 callback per minute, based  on what I know about our system. But your point is well taken. Personally, the most I&#8217;d wait is 2 seconds: thinking that if I don&#8217;t get a response after 2 seconds, it&#8217;s not going to happen. If a person was really concerned about performance then this would not be a good solution. Probably they would want to use dbms_jobs. What would you do?<br />
Regards,<br />
Mike</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: VJ</title>
		<link>http://hicamel.wordpress.com/2007/06/05/application-cache-refresh-call-back-trigger/#comment-55</link>
		<dc:creator>VJ</dc:creator>
		<pubDate>Thu, 14 Jun 2007 12:34:51 +0000</pubDate>
		<guid isPermaLink="false">http://hicamel.wordpress.com/2007/06/05/application-cache-refresh-call-back-trigger/#comment-55</guid>
		<description>If I understand your code correctly, for each row update,  you would have to wait for five seconds at worst or hundreds of milliseconds at best (time needed to get a page from an app server).  It does not look like a good thing for performance.</description>
		<content:encoded><![CDATA[<p>If I understand your code correctly, for each row update,  you would have to wait for five seconds at worst or hundreds of milliseconds at best (time needed to get a page from an app server).  It does not look like a good thing for performance.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
