<?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: FirePHP: Tying together Firebug and PHP</title>
	<atom:link href="http://ajaxian.com/archives/firephp-tying-together-firebug-and-php/feed" rel="self" type="application/rss+xml" />
	<link>http://ajaxian.com/archives/firephp-tying-together-firebug-and-php</link>
	<description>Cleaning up the web with Ajax</description>
	<lastBuildDate>Thu, 09 Feb 2012 06:55:33 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.2</generator>
	<item>
		<title>By: oopstudios</title>
		<link>http://ajaxian.com/archives/firephp-tying-together-firebug-and-php/comment-page-1#comment-272765</link>
		<dc:creator>oopstudios</dc:creator>
		<pubDate>Mon, 13 Apr 2009 14:21:55 +0000</pubDate>
		<guid isPermaLink="false">http://ajaxian.com/?p=6520#comment-272765</guid>
		<description>I can see it&#039;s use for some developers, but seems to me like using a Claw Hammer to remove a screw, a bit OTT. Errors should *never* be output with a response, even in the development phase - if you forget to hide them when you release you run the very real risk of exposing your code secrets and vulnerabilities.

I say use http://php.net/set_error_handler to update logs in a protected area you can view online, and throw yourself an email to boot (for future errors)</description>
		<content:encoded><![CDATA[<p>I can see it&#8217;s use for some developers, but seems to me like using a Claw Hammer to remove a screw, a bit OTT. Errors should *never* be output with a response, even in the development phase &#8211; if you forget to hide them when you release you run the very real risk of exposing your code secrets and vulnerabilities.</p>
<p>I say use <a href="http://php.net/set_error_handler" rel="nofollow">http://php.net/set_error_handler</a> to update logs in a protected area you can view online, and throw yourself an email to boot (for future errors)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Darkimmortal</title>
		<link>http://ajaxian.com/archives/firephp-tying-together-firebug-and-php/comment-page-1#comment-272746</link>
		<dc:creator>Darkimmortal</dc:creator>
		<pubDate>Sat, 11 Apr 2009 01:26:57 +0000</pubDate>
		<guid isPermaLink="false">http://ajaxian.com/?p=6520#comment-272746</guid>
		<description>YOU&#039;RE ONLY FINDING OUT ABOUT THIS NOW? :O 

Its uses are limited though - any AJAX application without a proper error metadata system (which can be used for debugging) isn&#039;t very well coded.</description>
		<content:encoded><![CDATA[<p>YOU&#8217;RE ONLY FINDING OUT ABOUT THIS NOW? :O </p>
<p>Its uses are limited though &#8211; any AJAX application without a proper error metadata system (which can be used for debugging) isn&#8217;t very well coded.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: smith</title>
		<link>http://ajaxian.com/archives/firephp-tying-together-firebug-and-php/comment-page-1#comment-272723</link>
		<dc:creator>smith</dc:creator>
		<pubDate>Fri, 10 Apr 2009 12:57:57 +0000</pubDate>
		<guid isPermaLink="false">http://ajaxian.com/?p=6520#comment-272723</guid>
		<description>There are also libraries for non-PHP languages, including server-side JS:

http://www.firephp.org/Wiki/
http://nlsmith.com/projects/console

It&#039;s a great program. It would be nice to have Mozilla and other browser vendors adopt wildfire or a similar standard to allow this sort of thing everywhere.</description>
		<content:encoded><![CDATA[<p>There are also libraries for non-PHP languages, including server-side JS:</p>
<p><a href="http://www.firephp.org/Wiki/" rel="nofollow">http://www.firephp.org/Wiki/</a><br />
<a href="http://nlsmith.com/projects/console" rel="nofollow">http://nlsmith.com/projects/console</a></p>
<p>It&#8217;s a great program. It would be nice to have Mozilla and other browser vendors adopt wildfire or a similar standard to allow this sort of thing everywhere.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

