<?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: Promises with dojo &#8211; a lightweight alternative to dojo.Deferred</title>
	<atom:link href="http://jensarps.de/2010/02/03/promises-with-dojo-a-lightweight-alternative-to-dojo-deferred/feed/" rel="self" type="application/rss+xml" />
	<link>http://jensarps.de/2010/02/03/promises-with-dojo-a-lightweight-alternative-to-dojo-deferred/</link>
	<description></description>
	<lastBuildDate>Wed, 08 Sep 2010 17:47:53 +0200</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.4</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Jens Arps</title>
		<link>http://jensarps.de/2010/02/03/promises-with-dojo-a-lightweight-alternative-to-dojo-deferred/comment-page-1/#comment-497</link>
		<dc:creator>Jens Arps</dc:creator>
		<pubDate>Fri, 05 Feb 2010 09:53:17 +0000</pubDate>
		<guid isPermaLink="false">http://jensarps.de/?p=190#comment-497</guid>
		<description>&lt;a href=&quot;#comment-495&quot; rel=&quot;nofollow&quot;&gt;@Eugene Lazutkin&lt;/a&gt; 

Thanks for the pointer. Pretty in-depth conversation, so I&#039;ll have to continue reading it later ( == weekend ).</description>
		<content:encoded><![CDATA[<p><a href="#comment-495" rel="nofollow">@Eugene Lazutkin</a> </p>
<p>Thanks for the pointer. Pretty in-depth conversation, so I&#8217;ll have to continue reading it later ( == weekend ).</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Micheil Smith</title>
		<link>http://jensarps.de/2010/02/03/promises-with-dojo-a-lightweight-alternative-to-dojo-deferred/comment-page-1/#comment-496</link>
		<dc:creator>Micheil Smith</dc:creator>
		<pubDate>Fri, 05 Feb 2010 08:23:20 +0000</pubDate>
		<guid isPermaLink="false">http://jensarps.de/?p=190#comment-496</guid>
		<description>&lt;a href=&quot;#comment-493&quot; rel=&quot;nofollow&quot;&gt;@Jens Arps&lt;/a&gt; and &lt;a href=&quot;#comment-489&quot; rel=&quot;nofollow&quot;&gt;@ben hockey&lt;/a&gt;:

 I agree with Ben&#039;s version, it&#039;s much cleaner then my original modification.</description>
		<content:encoded><![CDATA[<p><a href="#comment-493" rel="nofollow">@Jens Arps</a> and <a href="#comment-489" rel="nofollow">@ben hockey</a>:</p>
<p> I agree with Ben&#8217;s version, it&#8217;s much cleaner then my original modification.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Eugene Lazutkin</title>
		<link>http://jensarps.de/2010/02/03/promises-with-dojo-a-lightweight-alternative-to-dojo-deferred/comment-page-1/#comment-495</link>
		<dc:creator>Eugene Lazutkin</dc:creator>
		<pubDate>Fri, 05 Feb 2010 04:51:08 +0000</pubDate>
		<guid isPermaLink="false">http://jensarps.de/?p=190#comment-495</guid>
		<description>Incidentally a possible &quot;event&quot;-based implementation was discussed in Dojo-Dev (http://article.gmane.org/gmane.comp.web.dojo.devel/12371) --- look for onCallback. That article contains other views and unanswered questions on a possible design of Promise.

I agree with you 100% that we have to find a synergy between different pieces of the toolkit (in this case AOP and Promise) in order to have an elegant cohesive solution, which is flexible and easy to use, rather than a bunch of independent yet inflexible and inconsistent blotches of code.</description>
		<content:encoded><![CDATA[<p>Incidentally a possible &#8220;event&#8221;-based implementation was discussed in Dojo-Dev (<a href="http://article.gmane.org/gmane.comp.web.dojo.devel/12371" rel="nofollow">http://article.gmane.org/gmane.comp.web.dojo.devel/12371</a>) &#8212; look for onCallback. That article contains other views and unanswered questions on a possible design of Promise.</p>
<p>I agree with you 100% that we have to find a synergy between different pieces of the toolkit (in this case AOP and Promise) in order to have an elegant cohesive solution, which is flexible and easy to use, rather than a bunch of independent yet inflexible and inconsistent blotches of code.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: uberVU - social comments</title>
		<link>http://jensarps.de/2010/02/03/promises-with-dojo-a-lightweight-alternative-to-dojo-deferred/comment-page-1/#comment-494</link>
		<dc:creator>uberVU - social comments</dc:creator>
		<pubDate>Fri, 05 Feb 2010 00:33:23 +0000</pubDate>
		<guid isPermaLink="false">http://jensarps.de/?p=190#comment-494</guid>
		<description>&lt;strong&gt;Social comments and analytics for this post...&lt;/strong&gt;

This post was mentioned on Twitter by jensarps: New blog post: Promises with dojo: a lightweight alternative to dojo.Deferred http://bit.ly/cpaVVj #dojo #promise...</description>
		<content:encoded><![CDATA[<p><strong>Social comments and analytics for this post&#8230;</strong></p>
<p>This post was mentioned on Twitter by jensarps: New blog post: Promises with dojo: a lightweight alternative to dojo.Deferred <a href="http://bit.ly/cpaVVj" rel="nofollow">http://bit.ly/cpaVVj</a> #dojo #promise&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jens Arps</title>
		<link>http://jensarps.de/2010/02/03/promises-with-dojo-a-lightweight-alternative-to-dojo-deferred/comment-page-1/#comment-493</link>
		<dc:creator>Jens Arps</dc:creator>
		<pubDate>Fri, 05 Feb 2010 00:02:33 +0000</pubDate>
		<guid isPermaLink="false">http://jensarps.de/?p=190#comment-493</guid>
		<description>&lt;a href=&quot;#comment-489&quot; rel=&quot;nofollow&quot;&gt;@ben hockey&lt;/a&gt; 

Interesting idea. I guess what you are aiming at is this:
&lt;a href=&quot;http://gist.github.com/295287&quot; rel=&quot;nofollow&quot;&gt;http://gist.github.com/295287&lt;/a&gt;

*Big* pro of that: No more unique id handling, no private _promiseId value.

A drawback would be that you&#039;d lose the possibility to distinguish the promises by that id and you couldn&#039;t hook onto the topics being published.

Bottom line is… hm, hard to say, but, personally, I&#039; go for the non-topic, direct-connect version you came up with because it is simpler and shorter.

Cool idea!</description>
		<content:encoded><![CDATA[<p><a href="#comment-489" rel="nofollow">@ben hockey</a> </p>
<p>Interesting idea. I guess what you are aiming at is this:<br />
<a href="http://gist.github.com/295287" rel="nofollow">http://gist.github.com/295287</a></p>
<p>*Big* pro of that: No more unique id handling, no private _promiseId value.</p>
<p>A drawback would be that you&#8217;d lose the possibility to distinguish the promises by that id and you couldn&#8217;t hook onto the topics being published.</p>
<p>Bottom line is… hm, hard to say, but, personally, I&#8217; go for the non-topic, direct-connect version you came up with because it is simpler and shorter.</p>
<p>Cool idea!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: ben hockey</title>
		<link>http://jensarps.de/2010/02/03/promises-with-dojo-a-lightweight-alternative-to-dojo-deferred/comment-page-1/#comment-489</link>
		<dc:creator>ben hockey</dc:creator>
		<pubDate>Thu, 04 Feb 2010 01:48:34 +0000</pubDate>
		<guid isPermaLink="false">http://jensarps.de/?p=190#comment-489</guid>
		<description>you could also skip the pub/sub and just use &#039;then&#039; to dojo.connect to &#039;emit&#039;.  emit would be an empty function and &#039;then&#039; would use connect in place of subscribe.  iirc, pub/sub uses connect under the covers.</description>
		<content:encoded><![CDATA[<p>you could also skip the pub/sub and just use &#8216;then&#8217; to dojo.connect to &#8216;emit&#8217;.  emit would be an empty function and &#8216;then&#8217; would use connect in place of subscribe.  iirc, pub/sub uses connect under the covers.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jens Arps</title>
		<link>http://jensarps.de/2010/02/03/promises-with-dojo-a-lightweight-alternative-to-dojo-deferred/comment-page-1/#comment-486</link>
		<dc:creator>Jens Arps</dc:creator>
		<pubDate>Wed, 03 Feb 2010 13:30:16 +0000</pubDate>
		<guid isPermaLink="false">http://jensarps.de/?p=190#comment-486</guid>
		<description>&lt;a href=&quot;#comment-485&quot; rel=&quot;nofollow&quot;&gt;@Micheil Smith&lt;/a&gt; 

Yes, that looks great! I really like the .emit() idea. It doesn&#039;t add too much to the code, and it makes it far more readable and easier to use/understand.

Thanks for this, I&#039;ll update the post with your modifications later today :)</description>
		<content:encoded><![CDATA[<p><a href="#comment-485" rel="nofollow">@Micheil Smith</a> </p>
<p>Yes, that looks great! I really like the .emit() idea. It doesn&#8217;t add too much to the code, and it makes it far more readable and easier to use/understand.</p>
<p>Thanks for this, I&#8217;ll update the post with your modifications later today <img src='http://jensarps.de/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /> </p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Micheil Smith</title>
		<link>http://jensarps.de/2010/02/03/promises-with-dojo-a-lightweight-alternative-to-dojo-deferred/comment-page-1/#comment-485</link>
		<dc:creator>Micheil Smith</dc:creator>
		<pubDate>Wed, 03 Feb 2010 13:13:11 +0000</pubDate>
		<guid isPermaLink="false">http://jensarps.de/?p=190#comment-485</guid>
		<description>Here&#039;s a version I quickly created based off what you have: http://gist.github.com/293591</description>
		<content:encoded><![CDATA[<p>Here&#8217;s a version I quickly created based off what you have: <a href="http://gist.github.com/293591" rel="nofollow">http://gist.github.com/293591</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Micheil Smith</title>
		<link>http://jensarps.de/2010/02/03/promises-with-dojo-a-lightweight-alternative-to-dojo-deferred/comment-page-1/#comment-484</link>
		<dc:creator>Micheil Smith</dc:creator>
		<pubDate>Wed, 03 Feb 2010 12:52:25 +0000</pubDate>
		<guid isPermaLink="false">http://jensarps.de/?p=190#comment-484</guid>
		<description>Some how I don&#039;t think this is the nicest API that could be used. Surely something like http://gist.github.com/293569 would be better? It wouldn&#039;t be too hard to implement and the code size difference would be minimal. It also lowers the level for figuring out how promises work and should be used.</description>
		<content:encoded><![CDATA[<p>Some how I don&#8217;t think this is the nicest API that could be used. Surely something like <a href="http://gist.github.com/293569" rel="nofollow">http://gist.github.com/293569</a> would be better? It wouldn&#8217;t be too hard to implement and the code size difference would be minimal. It also lowers the level for figuring out how promises work and should be used.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
