<?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; Adaptive</title>
	<atom:link href="http://www.davidpratten.com/tag/adaptive/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>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>
	</channel>
</rss>
