<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	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/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>David Pratten &#187; RBDC</title>
	<atom:link href="http://www.davidpratten.com/tag/rbdc/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.davidpratten.com</link>
	<description>Interests, Ideas and Observations</description>
	<lastBuildDate>Tue, 18 May 2010 00:49:55 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
			<item>
		<title>Internet All The Way Down</title>
		<link>http://www.davidpratten.com/2008/03/20/internet-all-the-way-down/</link>
		<comments>http://www.davidpratten.com/2008/03/20/internet-all-the-way-down/#comments</comments>
		<pubDate>Thu, 20 Mar 2008 09:40:58 +0000</pubDate>
		<dc:creator>david</dc:creator>
				<category><![CDATA[HyperText Computer]]></category>
		<category><![CDATA[RBDC]]></category>

		<guid isPermaLink="false">http://www.davidpratten.com/2008/03/20/internet-all-the-way-down/</guid>
		<description><![CDATA[&#8220;STEPS Toward The Reinvention of Programming&#8221;[linkmoved] has a great piece about the promise of a uniform model of computation based on arbitrary decomposition to the internet. On p32 they say:
Part of the solution to “an Internet all the way down” has interesting conflicts with today’s hardware and we are curious to see just how far this can be taken without having to posit a different (but pretty minimal) set of machinery to help out. Basically, we would like to make a distributed object system that is (a) so protected that it can allow completely foreign objects to be brought in from elsewhere without causing harm, and (b) so efficient that a much higher level of abstract communication can be used between objects (perhaps an advanced form of “publish and subscribe” or “forward inferencing using knowledge patterns”).
One of the central observations underlying RDBC (and Hypertext Computing) is just this idea of the Internet All the Way Down!
]]></description>
		<wfw:commentRss>http://www.davidpratten.com/2008/03/20/internet-all-the-way-down/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Adaptive control of Request Based Distributed Computing</title>
		<link>http://www.davidpratten.com/2008/02/09/adaptive-control-of-request-based-distributed-computing/</link>
		<comments>http://www.davidpratten.com/2008/02/09/adaptive-control-of-request-based-distributed-computing/#comments</comments>
		<pubDate>Sat, 09 Feb 2008 11:33:01 +0000</pubDate>
		<dc:creator>david</dc:creator>
				<category><![CDATA[Adaptive]]></category>
		<category><![CDATA[autonomic]]></category>
		<category><![CDATA[HyperText Computer]]></category>
		<category><![CDATA[RBDC]]></category>

		<guid isPermaLink="false">http://www.davidpratten.com/2008/02/09/adaptive-control-of-request-based-distributed-computing/</guid>
		<description><![CDATA[The purpose of this post is to illustrate the possibility for autonomic computing inherent in Request Based Distributed Computing (RBDC).  
This is how I summarised RBDC in a recent post:
Request Based Distributed Computing is a small extension of the http protocol and notion of server, proxy and client. Rich Internet Applications, SOA architected applications and SETI@home type distributed computing alike can utilise a common unified programming model. No longer will technology dictate the locus of code execution &#8211; instead issues like availability of computing power, intellectual property and security will dictate this at run time.
This discussion focuses on the way that RBDC creates two ways to satisfy many http requests. The two ways are illustrated in the following two diagrams.  These diagrams are similar to those in a earlier discussion.
In the first scenario (DIAGRAM 1) we see a client requesting resource A and evaluating code locally to satisfy its own http request.
DIAGRAM 1
In the second scenario (DIAGRAM 2) we see the same client.  However in this case, when the client requests resource A, the client does not tell the server about it&#8217;s local computing capacity. In this case the relevant code is evaluated on the server.
DIAGRAM 2
The [...]]]></description>
		<wfw:commentRss>http://www.davidpratten.com/2008/02/09/adaptive-control-of-request-based-distributed-computing/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Tier-Agnostic Requests and Wadi</title>
		<link>http://www.davidpratten.com/2008/02/09/tier-agnostic-requests-and-wadi/</link>
		<comments>http://www.davidpratten.com/2008/02/09/tier-agnostic-requests-and-wadi/#comments</comments>
		<pubDate>Sat, 09 Feb 2008 06:59:33 +0000</pubDate>
		<dc:creator>david</dc:creator>
				<category><![CDATA[HyperText Computer]]></category>
		<category><![CDATA[RBDC]]></category>
		<category><![CDATA[requests]]></category>
		<category><![CDATA[tier agnostic]]></category>
		<category><![CDATA[wadi]]></category>

		<guid isPermaLink="false">http://www.davidpratten.com/2008/02/09/tier-agnostic-requests-and-wadi/</guid>
		<description><![CDATA[Tier-Agnostic requests are being used by the Wadi project in Java Server Farms. This Java-specific implementation lends support to the general applicability of Request Based Distributed Computing (RBDC) for client centric distributed computing.
WADI is an acronym of &#8216;WADI Application Distribution Infrastructure&#8217;. WADI started life as a solution to the problems surrounding the distribution of state in clustered web tiers. It has evolved into a more generalised distributed state and service framework. 
The Wadi Docs describe an Invocation mechanism that shares features with RBDC. The Invocation Interface is a tier-agnostic encapsulation of a remote call. Here is a first-cut comparison:
Similarities

Both use the idea of Tier-Agnostic Requests
They have similar session-state mechanisms.  See here for one proposal about state within RBDC.
Both delay location of computing decisions until run-time.

Differences

Wadi is targeted for use within a server farm, where as RBDC is proposed as starting in the client and works into the server farm with the same mechanism.
Wadi maintains centralised knowledge of the location of active Java objects whereas RBDC works as an extension of http&#8217;s native request by request invocation pattern.
Wadi is programmed specifically for Java, RBDC is proposed as a generic mechansim.
Wadi is visible to the Java programmer. RBDC is proposed as [...]]]></description>
		<wfw:commentRss>http://www.davidpratten.com/2008/02/09/tier-agnostic-requests-and-wadi/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>RBDC Illustrated</title>
		<link>http://www.davidpratten.com/2008/02/06/rbdc-illustrated/</link>
		<comments>http://www.davidpratten.com/2008/02/06/rbdc-illustrated/#comments</comments>
		<pubDate>Wed, 06 Feb 2008 17:25:32 +0000</pubDate>
		<dc:creator>david</dc:creator>
				<category><![CDATA[Browser]]></category>
		<category><![CDATA[Distributed]]></category>
		<category><![CDATA[HyperText Computer]]></category>
		<category><![CDATA[RBDC]]></category>
		<category><![CDATA[VM]]></category>

		<guid isPermaLink="false">http://www.davidpratten.com/2008/02/06/rbdc-illustrated/</guid>
		<description><![CDATA[The purpose of this post is to illustrate the behaviour of Request Based Distributed Computing (RBDC).  This is how I summarised RBDC in a recent post:
Request Based Distributed Computing is a small extension of the http protocol and notion of server, proxy and client. Rich Internet Applications, SOA architected applications and SETI@home type distributed computing alike can utilise a common unified programming model. No longer will technology dictate the locus of code execution &#8211; instead issues like availability of computing power, intellectual property and security will dictate this at run time.
Using the mechanisms explained below the need for separate programming models on server and client is removed.  RDBC is language neutral, but for illustration purposes, in the following example lets assume that the server code is written in PHP.
Distributed computing may be facilitated by mobile code moving from the server to a browser that is equipped with one or more RBDC compatible Virtual Machines. In Diagram 1 the example Virtual Machines (VMs) are in circles labeled &#8220;hXXX&#8221; one for each of 3 major web environments. The VM&#8217;s in server and client are identical. Notice that the server does not return the requested &#8220;Resource A&#8221;, but rather the code [...]]]></description>
		<wfw:commentRss>http://www.davidpratten.com/2008/02/06/rbdc-illustrated/feed/</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
	</channel>
</rss>
