<?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 for DBJ.ORG</title>
	<atom:link href="http://dbj.org/dbj/?feed=comments-rss2" rel="self" type="application/rss+xml" />
	<link>http://dbj.org/dbj</link>
	<description>Creative Disruptive Feasible</description>
	<lastBuildDate>Mon, 23 Aug 2010 07:43:51 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0.1</generator>
	<item>
		<title>Comment on JSON considered unsafe ? by Dusan</title>
		<link>http://dbj.org/dbj/?p=90&#038;cpage=1#comment-710</link>
		<dc:creator>Dusan</dc:creator>
		<pubDate>Mon, 23 Aug 2010 07:43:51 +0000</pubDate>
		<guid isPermaLink="false">http://x.dbjsystems.com/blog/?p=90#comment-710</guid>
		<description>I am not 100% sure about YQL Cross Domain, but it should be pretty easy to knock up a page at (for example) JSBIN, to test this.
Just include &quot;jQuery latest&quot; and fire away...</description>
		<content:encoded><![CDATA[<p>I am not 100% sure about YQL Cross Domain, but it should be pretty easy to knock up a page at (for example) JSBIN, to test this.<br />
Just include &#8220;jQuery latest&#8221; and fire away&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on JSON considered unsafe ? by Raman</title>
		<link>http://dbj.org/dbj/?p=90&#038;cpage=1#comment-709</link>
		<dc:creator>Raman</dc:creator>
		<pubDate>Mon, 23 Aug 2010 07:29:33 +0000</pubDate>
		<guid isPermaLink="false">http://x.dbjsystems.com/blog/?p=90#comment-709</guid>
		<description>Your argument makes sense. Would this security flaw in JSON apply to Cross Domain YQL pulls? I am not a professional but only a dabbler, and my current interest is cross domain ajax. Thanks.</description>
		<content:encoded><![CDATA[<p>Your argument makes sense. Would this security flaw in JSON apply to Cross Domain YQL pulls? I am not a professional but only a dabbler, and my current interest is cross domain ajax. Thanks.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Single Setup (SS) by Steven young</title>
		<link>http://dbj.org/dbj/?p=46&#038;cpage=1#comment-706</link>
		<dc:creator>Steven young</dc:creator>
		<pubDate>Thu, 19 Aug 2010 15:45:51 +0000</pubDate>
		<guid isPermaLink="false">http://x.dbjsystems.com/blog/?p=46#comment-706</guid>
		<description>cool</description>
		<content:encoded><![CDATA[<p>cool</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on RFC : CallStream as an Interfacing Concept by Dusan</title>
		<link>http://dbj.org/dbj/?p=757&#038;cpage=1#comment-691</link>
		<dc:creator>Dusan</dc:creator>
		<pubDate>Sun, 04 Jul 2010 19:32:20 +0000</pubDate>
		<guid isPermaLink="false">http://dbj.org/dbj/?p=757#comment-691</guid>
		<description>@Dmitry, thanks for the short analysis. Of course I know that you do understand how nicely callbacks significance gets elevated even more when using them in the CallStream enabled interefacing.
[sourcecode lang=&quot;jscript&quot;]
nodes(10, 20) (30, 40) (50, 60)(do_with_nodes_so_far);
[/sourcecode]
I am sure You will be very interested in this too :

http://weblogs.asp.net/bleroy/archive/2010/07/01/oh-yeah-callstream-is-great-to-express-monads.aspx

--DBJ</description>
		<content:encoded><![CDATA[<p>@Dmitry, thanks for the short analysis. Of course I know that you do understand how nicely callbacks significance gets elevated even more when using them in the CallStream enabled interefacing.</p>
<pre class="brush: jscript;">
nodes(10, 20) (30, 40) (50, 60)(do_with_nodes_so_far);
</pre>
<p>I am sure You will be very interested in this too :</p>
<p><a href="http://weblogs.asp.net/bleroy/archive/2010/07/01/oh-yeah-callstream-is-great-to-express-monads.aspx" rel="nofollow">http://weblogs.asp.net/bleroy/archive/2010/07/01/oh-yeah-callstream-is-great-to-express-monads.aspx</a></p>
<p>&#8211;DBJ</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on RFC : CallStream as an Interfacing Concept by Dmitry A. Soshnikov</title>
		<link>http://dbj.org/dbj/?p=757&#038;cpage=1#comment-690</link>
		<dc:creator>Dmitry A. Soshnikov</dc:creator>
		<pubDate>Sun, 04 Jul 2010 18:55:44 +0000</pubDate>
		<guid isPermaLink="false">http://dbj.org/dbj/?p=757#comment-690</guid>
		<description>Hi Dusan,

Yeah, this is interesting concept, thanks for research. In the functional programming it&#039;s called a &lt;em&gt;self-reproducible&lt;/em&gt; or &lt;em&gt;self-replicative&lt;/em&gt; function (if interested, I mention it in closures article -- http://dmitrysoshnikov.com/ecmascript/chapter-6-closures/#definitions).

Another interesting application of such self-replicative function can be e.g. declarative form of registering some data. E.g. instead of having (semantically) two functions:
[sourcecode language=&quot;javascript&quot;]
function defineNode(node) {
  ...
}
[/sourcecode]
and
[sourcecode language=&quot;javascript&quot;]
function defineNodes(nodes) {
  // nodes is an array
  for (...) {
    defineNode(nodes[k]);
  }
}

// single
defineNode([10, 20]);

// multiple
definedNodes([
  [30, 40],
  [50, 60],
  // etc.
])
[/sourcecode]
It can one self-replicative and declarative &lt;em&gt;nodes&lt;/em&gt; function. So, we just declare nodes:
[sourcecode language=&quot;javascript&quot;]
nodes 
  (10, 20)
  (30, 40)
  (50, 60);
[/sourcecode]
Of course, it&#039;s less effective than passing an array, but, repeat -- just an interesting an d maybe elegant approach (I saw it before in c.l.javascript group).

However, didn&#039;t use in on practice myself yet.

Dmitry.</description>
		<content:encoded><![CDATA[<p>Hi Dusan,</p>
<p>Yeah, this is interesting concept, thanks for research. In the functional programming it&#8217;s called a <em>self-reproducible</em> or <em>self-replicative</em> function (if interested, I mention it in closures article &#8212; <a href="http://dmitrysoshnikov.com/ecmascript/chapter-6-closures/#definitions)" rel="nofollow">http://dmitrysoshnikov.com/ecmascript/chapter-6-closures/#definitions)</a>.</p>
<p>Another interesting application of such self-replicative function can be e.g. declarative form of registering some data. E.g. instead of having (semantically) two functions:</p>
<pre class="brush: jscript;">
function defineNode(node) {
  ...
}
</pre>
<p>and</p>
<pre class="brush: jscript;">
function defineNodes(nodes) {
  // nodes is an array
  for (...) {
    defineNode(nodes[k]);
  }
}

// single
defineNode([10, 20]);

// multiple
definedNodes([
  [30, 40],
  [50, 60],
  // etc.
])
</pre>
<p>It can one self-replicative and declarative <em>nodes</em> function. So, we just declare nodes:</p>
<pre class="brush: jscript;">
nodes
  (10, 20)
  (30, 40)
  (50, 60);
</pre>
<p>Of course, it&#8217;s less effective than passing an array, but, repeat &#8212; just an interesting an d maybe elegant approach (I saw it before in c.l.javascript group).</p>
<p>However, didn&#8217;t use in on practice myself yet.</p>
<p>Dmitry.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
