<?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: ActionScript 3.0 Chain of Responsibility Design Pattern: Decoupling Request and Request Handler</title>
	<atom:link href="http://www.as3dp.com/2008/01/14/actionscript-30-chain-of-responsibility-design-pattern-decoupling-request-and-request-handler/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.as3dp.com/2008/01/14/actionscript-30-chain-of-responsibility-design-pattern-decoupling-request-and-request-handler/</link>
	<description>OOP for Flash, Flex and AIR</description>
	<pubDate>Thu, 24 Jul 2008 07:25:38 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.6</generator>
		<item>
		<title>By: Bill Sanders</title>
		<link>http://www.as3dp.com/2008/01/14/actionscript-30-chain-of-responsibility-design-pattern-decoupling-request-and-request-handler/#comment-414</link>
		<dc:creator>Bill Sanders</dc:creator>
		<pubDate>Tue, 15 Jan 2008 12:50:59 +0000</pubDate>
		<guid isPermaLink="false">http://www.as3dp.com/2008/01/14/actionscript-30-chain-of-responsibility-design-pattern-decoupling-request-and-request-handler/#comment-414</guid>
		<description>Hi Timbot,

Thanks man. I'm trying not to go off half-cocked on these new (to me) DPs.

When working on CoR, I kept thinking that there's a lot of different ways that this can be done, and my solution is only one of many. Chandima and I welcome lots of different ideas, and if you could generate a sample CoR with your idea, we could put it up for discussion.

Also, I think it would be helpful to work with requests that involved different kinds of request objects. Numeric requests are pretty simple (that's why I used one!) and I don't think it'd be too difficult to cook up something interesting if any readers here would be interested in playing around with some ideas.

Bill</description>
		<content:encoded><![CDATA[<p>Hi Timbot,</p>
<p>Thanks man. I&#8217;m trying not to go off half-cocked on these new (to me) DPs.</p>
<p>When working on CoR, I kept thinking that there&#8217;s a lot of different ways that this can be done, and my solution is only one of many. Chandima and I welcome lots of different ideas, and if you could generate a sample CoR with your idea, we could put it up for discussion.</p>
<p>Also, I think it would be helpful to work with requests that involved different kinds of request objects. Numeric requests are pretty simple (that&#8217;s why I used one!) and I don&#8217;t think it&#8217;d be too difficult to cook up something interesting if any readers here would be interested in playing around with some ideas.</p>
<p>Bill</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Timbot</title>
		<link>http://www.as3dp.com/2008/01/14/actionscript-30-chain-of-responsibility-design-pattern-decoupling-request-and-request-handler/#comment-413</link>
		<dc:creator>Timbot</dc:creator>
		<pubDate>Tue, 15 Jan 2008 05:45:45 +0000</pubDate>
		<guid isPermaLink="false">http://www.as3dp.com/2008/01/14/actionscript-30-chain-of-responsibility-design-pattern-decoupling-request-and-request-handler/#comment-413</guid>
		<description>This is a great explanation.  Well done!
The handlers remind me of a singly-linked list, and the request class makes me think of a value object.  Perhaps you could employ a linked list where each node held a reference to a handler that could be applied to the request.
In this way, you could insert of remove handlers from the chain of responsibility at runtime.  (Of course, you could add such functionality to the handler superclass as well.  I think either would be good solutions yes?)
-t.</description>
		<content:encoded><![CDATA[<p>This is a great explanation.  Well done!<br />
The handlers remind me of a singly-linked list, and the request class makes me think of a value object.  Perhaps you could employ a linked list where each node held a reference to a handler that could be applied to the request.<br />
In this way, you could insert of remove handlers from the chain of responsibility at runtime.  (Of course, you could add such functionality to the handler superclass as well.  I think either would be good solutions yes?)<br />
-t.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

<!-- Dynamic Page Served (once) in 0.392 seconds -->
