<?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: Creating your own RPC-interface in PHP</title>
	<atom:link href="http://syntacticsugar.nl/2009/04/17/creating-your-own-rpc-interface-in-php/feed/" rel="self" type="application/rss+xml" />
	<link>http://syntacticsugar.nl/2009/04/17/creating-your-own-rpc-interface-in-php/</link>
	<description>Random ramblings of another web-techy</description>
	<lastBuildDate>Fri, 20 Aug 2010 16:58:56 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.1</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Clark</title>
		<link>http://syntacticsugar.nl/2009/04/17/creating-your-own-rpc-interface-in-php/comment-page-1/#comment-4028</link>
		<dc:creator>Clark</dc:creator>
		<pubDate>Sun, 18 Oct 2009 10:57:50 +0000</pubDate>
		<guid isPermaLink="false">http://syntacticsugar.nl/?p=142#comment-4028</guid>
		<description>With respect to your function that tried using fsockopen, I have found that some servers are more persnickety than others in what they will accept as far as headers.  Primarily, \r\n is the expected newline pattern, not just \n, so the server might not be translating the commands properly, but just as important is knowing exactly which headers to send.  Generally, I&#039;ll start with a set of headers recently sent by my browser (intercepted with something like Tamper-Data or Live HTTP Headers for Firefox) and whittle those down to the smallest set that the target machine will accept.

At any rate, your article pleased me, and may I say &quot;Good Show, sir&quot;</description>
		<content:encoded><![CDATA[<p>With respect to your function that tried using fsockopen, I have found that some servers are more persnickety than others in what they will accept as far as headers.  Primarily, \r\n is the expected newline pattern, not just \n, so the server might not be translating the commands properly, but just as important is knowing exactly which headers to send.  Generally, I&#8217;ll start with a set of headers recently sent by my browser (intercepted with something like Tamper-Data or Live HTTP Headers for Firefox) and whittle those down to the smallest set that the target machine will accept.</p>
<p>At any rate, your article pleased me, and may I say &#8220;Good Show, sir&#8221;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Creating your own RPC-interface in PHP &#124; Syntactic sugar - 【23php】</title>
		<link>http://syntacticsugar.nl/2009/04/17/creating-your-own-rpc-interface-in-php/comment-page-1/#comment-526</link>
		<dc:creator>Creating your own RPC-interface in PHP &#124; Syntactic sugar - 【23php】</dc:creator>
		<pubDate>Sat, 18 Apr 2009 04:24:27 +0000</pubDate>
		<guid isPermaLink="false">http://syntacticsugar.nl/?p=142#comment-526</guid>
		<description>[...] post:  Creating your own RPC-interface in PHP &#124; Syntactic sugar   Tags:and-join, new-rpc, Object, PHP Array, powered, proudly-powered, the-fun Category:Object, PHP [...]</description>
		<content:encoded><![CDATA[<p>[...] post:  Creating your own RPC-interface in PHP | Syntactic sugar   Tags:and-join, new-rpc, Object, PHP Array, powered, proudly-powered, the-fun Category:Object, PHP [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>
