<?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: Invoking FoF with WGET</title>
	<atom:link href="http://gfmorris.com/2004/10/29/invoking-fof-with-wget/feed/" rel="self" type="application/rss+xml" />
	<link>http://gfmorris.com/2004/10/29/invoking-fof-with-wget/</link>
	<description>The Life and Times of Geof F. Morris</description>
	<lastBuildDate>Sun, 21 Mar 2010 17:52:32 -0500</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Jeff</title>
		<link>http://gfmorris.com/2004/10/29/invoking-fof-with-wget/comment-page-1/#comment-3536</link>
		<dc:creator>Jeff</dc:creator>
		<pubDate>Sat, 30 Oct 2004 14:34:19 +0000</pubDate>
		<guid isPermaLink="false">http://ijsm.org/archives/2004/10/29/invoking-fof-with-wget/#comment-3536</guid>
		<description>While it&#039;s true that the &quot;update-quiet.php&quot; script is grabbing files, it does that the same way no matter how it&#039;s called. As far as the web server is concerned, there shouldn&#039;t be any difference between using GET and wget. Both produce the same result: sending a single HTTP GET command to the web server. From there, it&#039;s the web server, not GET or wget, that does the work in grabbing the feeds. What wget is doing is saving the output from the webserver (the output of update-quiet.php, which is nothing) to a file. That&#039;s one problem with using wget here: you end up with a pile of empty &quot;update-quiet.php.[rotated integer]&quot; files saved to your home directory.

That being said, it&#039;s interesting that you saw a difference in speed between the two. I just tried it myself (by running each one multiple times). From what I saw, any difference between using GET and wget was completely swallowed by the variable delay encountered by the web server as it tried to fetch the feed data. In other words, in a horse race, either one of them might win, depending on how long it took the web server to fetch the data on that particular run.</description>
		<content:encoded><![CDATA[<p>While it&#8217;s true that the &#8220;update-quiet.php&#8221; script is grabbing files, it does that the same way no matter how it&#8217;s called. As far as the web server is concerned, there shouldn&#8217;t be any difference between using GET and wget. Both produce the same result: sending a single HTTP GET command to the web server. From there, it&#8217;s the web server, not GET or wget, that does the work in grabbing the feeds. What wget is doing is saving the output from the webserver (the output of update-quiet.php, which is nothing) to a file. That&#8217;s one problem with using wget here: you end up with a pile of empty &#8220;update-quiet.php.[rotated integer]&#8221; files saved to your home directory.</p>
<p>That being said, it&#8217;s interesting that you saw a difference in speed between the two. I just tried it myself (by running each one multiple times). From what I saw, any difference between using GET and wget was completely swallowed by the variable delay encountered by the web server as it tried to fetch the feed data. In other words, in a horse race, either one of them might win, depending on how long it took the web server to fetch the data on that particular run.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
