<?xml version="1.0"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
	<id>http://mw.hh.se/wg211/index.php?action=history&amp;feed=atom&amp;title=WG211%2FM7Cook</id>
	<title>WG211/M7Cook - Revision history</title>
	<link rel="self" type="application/atom+xml" href="http://mw.hh.se/wg211/index.php?action=history&amp;feed=atom&amp;title=WG211%2FM7Cook"/>
	<link rel="alternate" type="text/html" href="http://mw.hh.se/wg211/index.php?title=WG211/M7Cook&amp;action=history"/>
	<updated>2026-04-06T01:00:33Z</updated>
	<subtitle>Revision history for this page on the wiki</subtitle>
	<generator>MediaWiki 1.43.5</generator>
	<entry>
		<id>http://mw.hh.se/wg211/index.php?title=WG211/M7Cook&amp;diff=225&amp;oldid=prev</id>
		<title>Admin: 1 revision</title>
		<link rel="alternate" type="text/html" href="http://mw.hh.se/wg211/index.php?title=WG211/M7Cook&amp;diff=225&amp;oldid=prev"/>
		<updated>2011-12-12T10:06:27Z</updated>

		<summary type="html">&lt;p&gt;1 revision&lt;/p&gt;
&lt;p&gt;&lt;b&gt;New page&lt;/b&gt;&lt;/p&gt;&lt;div&gt;[[Category:WG211]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&amp;lt;h1&amp;gt;Slice, Partition, and Reforest for Data Access and Distribution&amp;lt;/h1&amp;gt;&lt;br /&gt;
&amp;lt;h3&amp;gt;William R. Cook&amp;lt;/h3&amp;gt;&lt;br /&gt;
&lt;br /&gt;
One of the problems with Remote Procedure Calls (RPC) is that they are&lt;br /&gt;
&amp;lt;i&amp;gt;latency additive&amp;lt;/i&amp;gt;, meaning that two calls F(G(x)) take twice as long&lt;br /&gt;
as a single call to a combined procedure FG(x). We introduce a new&lt;br /&gt;
&amp;lt;tt&amp;gt;batch&amp;lt;/tt&amp;gt; statement used by clients to compose remote calls into a&lt;br /&gt;
single batch for remote execution, with support for sequential composition,&lt;br /&gt;
conditionals and loops. More interestingly, batches allow client and remote&lt;br /&gt;
computations to be mixed together. The remote computations in a batch are&lt;br /&gt;
separated from the location computations and executed in a single remote&lt;br /&gt;
service call. The partition is computed using a binding location analysis&lt;br /&gt;
similar to binding time analysis. Finally, the primitive data transfered to&lt;br /&gt;
and from the remote server is sent in bulk as an intermediate tree structure&lt;br /&gt;
defined by &amp;lt;i&amp;gt;reforestation&amp;lt;/i&amp;gt;, a new concept that is the inverse of&lt;br /&gt;
deforestation. For traditional distributed object systems (RMI and CORBA),&lt;br /&gt;
batches obviate the need for proxies and allow Data Transfer Objects and&lt;br /&gt;
Server Facades to be created on the fly for fine-grained server interfaces.&lt;br /&gt;
Batches are also equivalent to document-oriented Web Services, but provide a&lt;br /&gt;
simpler and more flexible programming model. Finally, we suggest that&lt;br /&gt;
batches may be an ideal interface to databases. In conclusion, the batch statement is a general-purpose programming construct for program partitioning and reforestation with many applications.&lt;br /&gt;
&lt;br /&gt;
* [[Media:2009-Batches-WG211.pdf | 2009-Batches-WG211.pdf ]]: Slides&lt;br /&gt;
&lt;br /&gt;
==File Attachments== &lt;br /&gt;
&lt;br /&gt;
*[[Media:2009-Batches-WG211.pdf | 2009-Batches-WG211.pdf]]&lt;/div&gt;</summary>
		<author><name>Admin</name></author>
	</entry>
</feed>