<?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: Exceptions From a User&#8217;s Perspective</title>
	<atom:link href="http://eclipsesource.com/blogs/2009/01/29/exceptions-from-a-users-perspective/feed/" rel="self" type="application/rss+xml" />
	<link>http://eclipsesource.com/blogs/2009/01/29/exceptions-from-a-users-perspective/</link>
	<description>Eclipse Equinox OSGi</description>
	<lastBuildDate>Sat, 20 Mar 2010 02:14:33 +0100</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: manuel</title>
		<link>http://eclipsesource.com/blogs/2009/01/29/exceptions-from-a-users-perspective/comment-page-1/#comment-466</link>
		<dc:creator>manuel</dc:creator>
		<pubDate>Tue, 10 Feb 2009 07:20:07 +0000</pubDate>
		<guid isPermaLink="false">http://eclipsesource.com/blogs/?p=259#comment-466</guid>
		<description>Sorry for the late reply.
While these thoughts apply in general, for the eclipse platform it might make sense to have some sort of automatic error reporting, sending the error details to a central database (after getting the user&#039;s consent of course). While this would require quite an up-front investment in infrastructure, the long-term benefits might be worth it. 
Due to the plugin philosophy we have a huge amount of possible configurations, and while that should work in theory, reality tends to rear its ugly heads in unexpected ways. Such an error database could help (among other things of course) pinpoint such incompatibilities and improve overall quality.</description>
		<content:encoded><![CDATA[<p>Sorry for the late reply.<br />
While these thoughts apply in general, for the eclipse platform it might make sense to have some sort of automatic error reporting, sending the error details to a central database (after getting the user&#8217;s consent of course). While this would require quite an up-front investment in infrastructure, the long-term benefits might be worth it.<br />
Due to the plugin philosophy we have a huge amount of possible configurations, and while that should work in theory, reality tends to rear its ugly heads in unexpected ways. Such an error database could help (among other things of course) pinpoint such incompatibilities and improve overall quality.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Boris Bokowski</title>
		<link>http://eclipsesource.com/blogs/2009/01/29/exceptions-from-a-users-perspective/comment-page-1/#comment-328</link>
		<dc:creator>Boris Bokowski</dc:creator>
		<pubDate>Fri, 30 Jan 2009 03:02:49 +0000</pubDate>
		<guid isPermaLink="false">http://eclipsesource.com/blogs/?p=259#comment-328</guid>
		<description>Great post! Is there anything we can take away from this, e.g. to improve the error handling and logging facilities that we have in Eclipse?</description>
		<content:encoded><![CDATA[<p>Great post! Is there anything we can take away from this, e.g. to improve the error handling and logging facilities that we have in Eclipse?</p>
]]></content:encoded>
	</item>
</channel>
</rss>
