<?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: Flex Remoting and WebORB Mysterious Error Messages</title>
	<atom:link href="http://www.verysimple.com/blog/2009/07/01/flex-remoting-and-weborb-mysterious-error-messages/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.verysimple.com/blog/2009/07/01/flex-remoting-and-weborb-mysterious-error-messages/</link>
	<description>Custom Software Development</description>
	<lastBuildDate>Mon, 08 Mar 2010 16:27:28 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=abc</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Jason</title>
		<link>http://www.verysimple.com/blog/2009/07/01/flex-remoting-and-weborb-mysterious-error-messages/comment-page-1/#comment-106723</link>
		<dc:creator>Jason</dc:creator>
		<pubDate>Wed, 01 Jul 2009 23:38:56 +0000</pubDate>
		<guid isPermaLink="false">http://www.verysimple.com/blog/?p=390#comment-106723</guid>
		<description>Very cool - thanks for stopping by Mark, I really love your WebORB products, by the way.  I will have to give AppPuncher a try, it sounds way better than my process-of-elimination approach.  The compile errors are almost always the result of a stupid typo buried deep inside a class (of my own code, not WebORB).  Being able to see the PHP output would make it trivial to fix those types of issues.</description>
		<content:encoded><![CDATA[<p>Very cool &#8211; thanks for stopping by Mark, I really love your WebORB products, by the way.  I will have to give AppPuncher a try, it sounds way better than my process-of-elimination approach.  The compile errors are almost always the result of a stupid typo buried deep inside a class (of my own code, not WebORB).  Being able to see the PHP output would make it trivial to fix those types of issues.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Mark Piller</title>
		<link>http://www.verysimple.com/blog/2009/07/01/flex-remoting-and-weborb-mysterious-error-messages/comment-page-1/#comment-106719</link>
		<dc:creator>Mark Piller</dc:creator>
		<pubDate>Wed, 01 Jul 2009 22:38:03 +0000</pubDate>
		<guid isPermaLink="false">http://www.verysimple.com/blog/?p=390#comment-106719</guid>
		<description>Thank you for the post, it is very helpful! One of the approaches we recommend in diagnosing PHP crashes is using AppPuncher (it is one of our own products). AppPuncher can visualize on-the-wire traffic including AMF. For a flex remoting call you can see the contents of the request, but if the response is not AMF, then the &#039;raw&#039; view will show the actual error PHP has encountered. 

p.s. you do not have to use AppPuncher and free to try any of the competing products</description>
		<content:encoded><![CDATA[<p>Thank you for the post, it is very helpful! One of the approaches we recommend in diagnosing PHP crashes is using AppPuncher (it is one of our own products). AppPuncher can visualize on-the-wire traffic including AMF. For a flex remoting call you can see the contents of the request, but if the response is not AMF, then the &#8216;raw&#8217; view will show the actual error PHP has encountered. </p>
<p>p.s. you do not have to use AppPuncher and free to try any of the competing products</p>
]]></content:encoded>
	</item>
</channel>
</rss>
