<?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"
	>
<channel>
	<title>Comments on: Error reports.  They&#8217;re everywhere&#8230;</title>
	<atom:link href="http://blog.getsatisfaction.com/2007/05/03/error-reports-theyre-everywhere/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.getsatisfaction.com/2007/05/03/error-reports-theyre-everywhere/</link>
	<description>The Get Satisfaction blog</description>
	<pubDate>Fri, 21 Nov 2008 18:36:24 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.6.1</generator>
		<item>
		<title>By: web</title>
		<link>http://blog.getsatisfaction.com/2007/05/03/error-reports-theyre-everywhere/#comment-425</link>
		<dc:creator>web</dc:creator>
		<pubDate>Fri, 04 May 2007 19:59:57 +0000</pubDate>
		<guid isPermaLink="false">http://blog.getsatisfaction.com/2007/05/03/error-reports-theyre-everywhere/#comment-425</guid>
		<description>Good idea, lots of people forget now that they are re-writing browser based functions in applications that they need to emulate all browser functions, not just the ones easy to do.

Lots of AJAX apps don't have browser back, forward access .. nor are they bookmark-able. If your not in it for the long haul, don't go at all.

A quick error reporting that I used before is to open an GET connection to a page I know that does not exist and then pass in a query string of the specific JavaScript error.

i.e. GET --&#62; /JavascriptErrors.html?error=no_data_incoming_from_XYZ_function

This way it shows up on your server error log which has thousands of reporting tools available to make us aware on whats going wrong.

An error is an error, lets not pretend they don't exist.

ps. New Reader, good eats. RSS feeds + 1</description>
		<content:encoded><![CDATA[<p>Good idea, lots of people forget now that they are re-writing browser based functions in applications that they need to emulate all browser functions, not just the ones easy to do.</p>
<p>Lots of AJAX apps don&#8217;t have browser back, forward access .. nor are they bookmark-able. If your not in it for the long haul, don&#8217;t go at all.</p>
<p>A quick error reporting that I used before is to open an GET connection to a page I know that does not exist and then pass in a query string of the specific JavaScript error.</p>
<p>i.e. GET &#8211;&gt; /JavascriptErrors.html?error=no_data_incoming_from_XYZ_function</p>
<p>This way it shows up on your server error log which has thousands of reporting tools available to make us aware on whats going wrong.</p>
<p>An error is an error, lets not pretend they don&#8217;t exist.</p>
<p>ps. New Reader, good eats. RSS feeds + 1</p>
]]></content:encoded>
	</item>
</channel>
</rss>
