# HG changeset patch
# User Nathan Phillip Brink <ohnobinki@ohnopublishing.net>
# Date 2010-08-08 00:19:54
# Node ID 12246b1661816e488d502e1c965be1e59f96881b
# Parent  c36100d8432d422152d535885ac533e59efddd34

Provide a basic model for job distribution.

diff --git a/doc/architecture.txt b/doc/architecture.txt
--- a/doc/architecture.txt
+++ b/doc/architecture.txt
@@ -29,6 +29,11 @@ Concepts:
       shall be responsible for collecting the individual completed frames and collecting them
       into a tarball. This tarball may be called for using a client. This tarball is a bundle
       of completed frames and will exclude the seed tarball.
+  - job announcement: When a job is created, the server it was submitted to shall make a
+      global announcement that the job is available. All servers should record this announcement
+      All servers will maintain a list of globally available jobs. When a server becomes available
+      to render a frame, it will scan the lists of announcements it has received and then ask
+      the originating server for a frame.
 
 - frame: Represents a distinct, and hopefully small, unit of work that a renderer backend can perform.
   - frame identification: Like a job numeral is useless without a qualifying servername, a 
diff --git a/doc/distrenjob.xml.example b/doc/distrenjob.xml.example
--- a/doc/distrenjob.xml.example
+++ b/doc/distrenjob.xml.example
@@ -44,7 +44,13 @@
 
     <!--
 	Currently, for simplicity, there will be a <frame /> tag for
-	every frame to be rendered.
+	every frame to be rendered. However, only the server from
+	which the job originates will see every such frame.
+	
+	When a server requests a frame, it shall receive a full
+	distrenjob.xml that contains only one frame. It will thus have
+	enough information to render that one frame and return its
+	results to the originating server.
     -->
     <frames>
       <frame name="distren://ohnopub.net/job/36/frame/23" />