<?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: Learning to crawl before you can run</title>
	<atom:link href="http://wheresrhys.co.uk/2009/07/learning-to-crawl-before-you-can-run/feed/" rel="self" type="application/rss+xml" />
	<link>http://wheresrhys.co.uk/2009/07/learning-to-crawl-before-you-can-run/</link>
	<description>on the internet</description>
	<lastBuildDate>Sat, 07 Apr 2012 14:54:41 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0.5</generator>
	<item>
		<title>By: wheresrhys</title>
		<link>http://wheresrhys.co.uk/2009/07/learning-to-crawl-before-you-can-run/comment-page-1/#comment-1918</link>
		<dc:creator>wheresrhys</dc:creator>
		<pubDate>Wed, 16 Sep 2009 06:29:41 +0000</pubDate>
		<guid isPermaLink="false">http://wheresrhys.co.uk/?p=732#comment-1918</guid>
		<description>My eventual solution to the timeout involved using AJAX to send the repeated requests, thereby allowing me to repeatedly reload the php page while keeping the browser window in the dark, so to speak, about what was going on. http://wheresrhys.co.uk/2009/08/geocoding-in-the-uk/. I did look into running scheduled tasks but my hosting provider wouldnt let me run scheduled php CGIs, which is why I turned t a browser reload solution.

I didnt use set_time_limit(0), though I think the issue is more to do with browsers not liking pages taht request themselves ad infinitum, rather than a problem with the page itself.</description>
		<content:encoded><![CDATA[<p>My eventual solution to the timeout involved using AJAX to send the repeated requests, thereby allowing me to repeatedly reload the php page while keeping the browser window in the dark, so to speak, about what was going on. <a href="http://wheresrhys.co.uk/2009/08/geocoding-in-the-uk/" rel="nofollow">http://wheresrhys.co.uk/2009/08/geocoding-in-the-uk/</a>. I did look into running scheduled tasks but my hosting provider wouldnt let me run scheduled php CGIs, which is why I turned t a browser reload solution.</p>
<p>I didnt use set_time_limit(0), though I think the issue is more to do with browsers not liking pages taht request themselves ad infinitum, rather than a problem with the page itself.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: gt</title>
		<link>http://wheresrhys.co.uk/2009/07/learning-to-crawl-before-you-can-run/comment-page-1/#comment-1890</link>
		<dc:creator>gt</dc:creator>
		<pubDate>Tue, 15 Sep 2009 01:11:25 +0000</pubDate>
		<guid isPermaLink="false">http://wheresrhys.co.uk/?p=732#comment-1890</guid>
		<description>I&#039;m faced with a similar problem for a website I&#039;m writing at the moment.

Have you looked at calling set_time_limit(0) to prevent the PHP engine from timing out?

Otherwise, your web host may allow &#039;scheduled tasks&#039; to be run via their admin pages, which could be used to re-start a PHP script every few minutes.</description>
		<content:encoded><![CDATA[<p>I&#8217;m faced with a similar problem for a website I&#8217;m writing at the moment.</p>
<p>Have you looked at calling set_time_limit(0) to prevent the PHP engine from timing out?</p>
<p>Otherwise, your web host may allow &#8216;scheduled tasks&#8217; to be run via their admin pages, which could be used to re-start a PHP script every few minutes.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

