<?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: Event Aggregation</title>
	<atom:link href="http://davybrion.com/blog/2009/10/event-aggregation/feed/" rel="self" type="application/rss+xml" />
	<link>http://davybrion.com/blog/2009/10/event-aggregation/</link>
	<description>Trying to walk that thin line between intelligence and ignorance</description>
	<lastBuildDate>Tue, 16 Mar 2010 15:10:50 +0100</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: kilfour</title>
		<link>http://davybrion.com/blog/2009/10/event-aggregation/comment-page-1/#comment-22719</link>
		<dc:creator>kilfour</dc:creator>
		<pubDate>Thu, 15 Oct 2009 13:14:46 +0000</pubDate>
		<guid isPermaLink="false">http://davybrion.com/blog/?p=1708#comment-22719</guid>
		<description>After using the EventAggregator for a couple of days now, I have to agree with putting the event declarations in a seperate namespace. ;-) 
Deciding to put them near the receiver, or near the one that calls publish, and what to do if the event gets thrown by different classes, induced a headache.
So an &#039;Events&#039; namespace it is.</description>
		<content:encoded><![CDATA[<p>After using the EventAggregator for a couple of days now, I have to agree with putting the event declarations in a seperate namespace. <img src='http://davybrion.com/blog/wp-includes/images/smilies/icon_wink.gif' alt=';-)' class='wp-smiley' /><br />
Deciding to put them near the receiver, or near the one that calls publish, and what to do if the event gets thrown by different classes, induced a headache.<br />
So an &#8216;Events&#8217; namespace it is.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Reflective Perspective - Chris Alcock &#187; The Morning Brew #452</title>
		<link>http://davybrion.com/blog/2009/10/event-aggregation/comment-page-1/#comment-22682</link>
		<dc:creator>Reflective Perspective - Chris Alcock &#187; The Morning Brew #452</dc:creator>
		<pubDate>Mon, 12 Oct 2009 07:42:30 +0000</pubDate>
		<guid isPermaLink="false">http://davybrion.com/blog/?p=1708#comment-22682</guid>
		<description>[...] Event Aggregation - Davy Brion explores the concepts and implementation of Event Aggregation Patterns for use in communicating occurrences to other parts of the code without caring about what those other parts are. [...]</description>
		<content:encoded><![CDATA[<p>[...] Event Aggregation &#8211; Davy Brion explores the concepts and implementation of Event Aggregation Patterns for use in communicating occurrences to other parts of the code without caring about what those other parts are. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Davy Brion</title>
		<link>http://davybrion.com/blog/2009/10/event-aggregation/comment-page-1/#comment-22681</link>
		<dc:creator>Davy Brion</dc:creator>
		<pubDate>Mon, 12 Oct 2009 07:00:33 +0000</pubDate>
		<guid isPermaLink="false">http://davybrion.com/blog/?p=1708#comment-22681</guid>
		<description>@Kilfour

i sort of agree on that... but the ability to type &quot;Events&quot; + &quot;.&quot; and have all the event types show up is pretty handy ;)</description>
		<content:encoded><![CDATA[<p>@Kilfour</p>
<p>i sort of agree on that&#8230; but the ability to type &#8220;Events&#8221; + &#8220;.&#8221; and have all the event types show up is pretty handy <img src='http://davybrion.com/blog/wp-includes/images/smilies/icon_wink.gif' alt=';)' class='wp-smiley' /> </p>
]]></content:encoded>
	</item>
	<item>
		<title>By: kilfour</title>
		<link>http://davybrion.com/blog/2009/10/event-aggregation/comment-page-1/#comment-22680</link>
		<dc:creator>kilfour</dc:creator>
		<pubDate>Mon, 12 Oct 2009 06:57:14 +0000</pubDate>
		<guid isPermaLink="false">http://davybrion.com/blog/?p=1708#comment-22680</guid>
		<description>Nice implementation.
Just a thought on &lt;i&gt;simply be grouped in separate namespaces/folders&lt;/i&gt;. I feel it&#039;s better to put classes in the namespaces where they are used, and I try to avoid using namespaces based on language features. I&#039;ve seen too many projects with an interfaces namespace, events namespace, views namespace, etc... Which usually means that if you&#039;re working on one thing, you need a corresponding other thing in each of the other namespaces.</description>
		<content:encoded><![CDATA[<p>Nice implementation.<br />
Just a thought on <i>simply be grouped in separate namespaces/folders</i>. I feel it&#8217;s better to put classes in the namespaces where they are used, and I try to avoid using namespaces based on language features. I&#8217;ve seen too many projects with an interfaces namespace, events namespace, views namespace, etc&#8230; Which usually means that if you&#8217;re working on one thing, you need a corresponding other thing in each of the other namespaces.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Davy Brion</title>
		<link>http://davybrion.com/blog/2009/10/event-aggregation/comment-page-1/#comment-22671</link>
		<dc:creator>Davy Brion</dc:creator>
		<pubDate>Sun, 11 Oct 2009 15:33:37 +0000</pubDate>
		<guid isPermaLink="false">http://davybrion.com/blog/?p=1708#comment-22671</guid>
		<description>definitely not an assembly per component... i use as few assemblies as possible: http://davybrion.com/blog/2008/07/many-projects-dont-lead-to-a-good-solution/

I expect most of the events will simply be grouped in separate namespaces/folders and that&#039;s about it.</description>
		<content:encoded><![CDATA[<p>definitely not an assembly per component&#8230; i use as few assemblies as possible: <a href="http://davybrion.com/blog/2008/07/many-projects-dont-lead-to-a-good-solution/" rel="nofollow">http://davybrion.com/blog/2008/07/many-projects-dont-lead-to-a-good-solution/</a></p>
<p>I expect most of the events will simply be grouped in separate namespaces/folders and that&#8217;s about it.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Benny Michielsen</title>
		<link>http://davybrion.com/blog/2009/10/event-aggregation/comment-page-1/#comment-22670</link>
		<dc:creator>Benny Michielsen</dc:creator>
		<pubDate>Sun, 11 Oct 2009 13:30:00 +0000</pubDate>
		<guid isPermaLink="false">http://davybrion.com/blog/?p=1708#comment-22670</guid>
		<description>How do you structure your project for the events themselves? Do they come in a single assembly, an assembly per component (SalesEvents, OrderEvents,...)</description>
		<content:encoded><![CDATA[<p>How do you structure your project for the events themselves? Do they come in a single assembly, an assembly per component (SalesEvents, OrderEvents,&#8230;)</p>
]]></content:encoded>
	</item>
</channel>
</rss>
