<?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: Porting a Java Program to PHP</title>
	<atom:link href="http://www.elharo.com/blog/software-development/2006/11/12/porting-a-java-program-to-php/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.elharo.com/blog/software-development/2006/11/12/porting-a-java-program-to-php/</link>
	<description>Ranting and Raving</description>
	<lastBuildDate>Thu, 18 Mar 2010 19:01:40 -0500</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.1</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: aaron brethorst</title>
		<link>http://www.elharo.com/blog/software-development/2006/11/12/porting-a-java-program-to-php/comment-page-1/#comment-38149</link>
		<dc:creator>aaron brethorst</dc:creator>
		<pubDate>Sun, 28 Jan 2007 23:43:28 +0000</pubDate>
		<guid isPermaLink="false">http://www.elharo.com/blog/software-development/2006/11/12/porting-a-java-program-to-php/#comment-38149</guid>
		<description>Thanks! I&#039;ve been running into the same problem, and it&#039;s been driving me nuts!</description>
		<content:encoded><![CDATA[<p>Thanks! I&#8217;ve been running into the same problem, and it&#8217;s been driving me nuts!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Elliotte Rusty Harold</title>
		<link>http://www.elharo.com/blog/software-development/2006/11/12/porting-a-java-program-to-php/comment-page-1/#comment-21114</link>
		<dc:creator>Elliotte Rusty Harold</dc:creator>
		<pubDate>Tue, 14 Nov 2006 10:54:50 +0000</pubDate>
		<guid isPermaLink="false">http://www.elharo.com/blog/software-development/2006/11/12/porting-a-java-program-to-php/#comment-21114</guid>
		<description>Aha! It is a client bug then. In this case the client is 

&lt;pre&gt;java version &quot;1.5.0_06&quot;
Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_06-112)
Java HotSpot(TM) Client VM (build 1.5.0_06-64, mixed mode, sharing)&lt;/pre&gt;

I&#039;ll have to file a bug report on this.</description>
		<content:encoded><![CDATA[<p>Aha! It is a client bug then. In this case the client is </p>
<pre>java version "1.5.0_06"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_06-112)
Java HotSpot(TM) Client VM (build 1.5.0_06-64, mixed mode, sharing)</pre>
<p>I&#8217;ll have to file a bug report on this.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Stephen</title>
		<link>http://www.elharo.com/blog/software-development/2006/11/12/porting-a-java-program-to-php/comment-page-1/#comment-20984</link>
		<dc:creator>Stephen</dc:creator>
		<pubDate>Mon, 13 Nov 2006 16:21:32 +0000</pubDate>
		<guid isPermaLink="false">http://www.elharo.com/blog/software-development/2006/11/12/porting-a-java-program-to-php/#comment-20984</guid>
		<description>Since you didn&#039;t specify the directory with a trailing slash, the server is sending a 301 Moved Permanently to the client, handing back a URL that ends in a slash. A URL like http://www.elharo.com/fibonacci/XML-RPC doesn&#039;t actually point to a valid location and most servers return the 301 instead of erroring out, the only other option they&#039;re allowed by the spec.

http://www.elharo.com/fibonacci/XML-RPC/ would probably have worked fine, too.

http://www.w3.org/Protocols/rfc2616/rfc2616-sec10.html

      Note: When automatically redirecting a POST request after
      receiving a 301 status code, some existing HTTP/1.0 user agents
      will erroneously change it into a GET request.</description>
		<content:encoded><![CDATA[<p>Since you didn&#8217;t specify the directory with a trailing slash, the server is sending a 301 Moved Permanently to the client, handing back a URL that ends in a slash. A URL like <a href="http://www.elharo.com/fibonacci/XML-RPC" rel="nofollow">http://www.elharo.com/fibonacci/XML-RPC</a> doesn&#8217;t actually point to a valid location and most servers return the 301 instead of erroring out, the only other option they&#8217;re allowed by the spec.</p>
<p><a href="http://www.elharo.com/fibonacci/XML-RPC/" rel="nofollow">http://www.elharo.com/fibonacci/XML-RPC/</a> would probably have worked fine, too.</p>
<p><a href="http://www.w3.org/Protocols/rfc2616/rfc2616-sec10.html" rel="nofollow">http://www.w3.org/Protocols/rfc2616/rfc2616-sec10.html</a></p>
<p>      Note: When automatically redirecting a POST request after<br />
      receiving a 301 status code, some existing HTTP/1.0 user agents<br />
      will erroneously change it into a GET request.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
