# HG changeset patch
# User Nathan Phillip Brink <ohnobinki@ohnopublishing.net>
# Date 2010-08-08 00:03:06
# Node ID c36100d8432d422152d535885ac533e59efddd34
# Parent  57a2c8251e446aa5b34aa0e1fa83873e3b67f8e6

Attempt to better define distrenjob.xml.

diff --git a/doc/distrenjob.xml.example b/doc/distrenjob.xml.example
--- a/doc/distrenjob.xml.example
+++ b/doc/distrenjob.xml.example
@@ -21,7 +21,7 @@
 <distren>
   <!-- is the priority option actually useful? -->
   <job
-     name="distren://ohnopub.net/job/"
+     name="distren://ohnopub.net/job/36"
      submitter="distren://ohnopub.net/user/binki"
      type="povray"
      >
@@ -29,13 +29,60 @@
     <!--
 	This tag is information that does not have to be present in
 	the original distrenjob.xml. For example, a povray's .ini file
-	may already specify this resolution information.
+	may already specify this resolution information. However,
+	information like this should be extracted because this
+	metadata may prove useful within distren's code. The <frames
+	/> tag is a better example, as povray's .ini file will specify
+	the information necessary for a sequence of frames to be
+	rendered and we need to actually intercept/override that
+	information.
     -->
     <resolution
        width="800"
        height="600"
        />
 
+    <!--
+	Currently, for simplicity, there will be a <frame /> tag for
+	every frame to be rendered.
+    -->
+    <frames>
+      <frame name="distren://ohnopub.net/job/36/frame/23" />
+
+      <!--
+	  As described in architecture.txt, we allow frame
+	  dependencies.
+      -->
+      <frame name="distren://ohnopub.net/job/36/frame/22">
+	<dep name="distren://ohnopub.net/job/36/frame/23" />
+	<dep name="distren://ohnopub.net/job/36/frame/24" />
+      </frame>
+
+      <frame name="distren://ohnopub.net/job/36/frame/24" />
+
+      <!--
+	  Assigned frames name their servers.
+      -->
+      <frame name="distren://ohnopub.net/job/36/frame/25"
+	     server="distren://protofusion.org/" />
+
+      <!--
+	  Finished frames name their files and servers. Note that the
+	  file's namespace is the job's URL. It is the job of the
+	  server that renders a file to push it to its originating
+	  server. It makes no sense for the originating server to try
+	  to collect files manually ;-). Also, for simplicity, a frame
+	  is considered assigned until the originating server obtains
+	  a copy of it.
+
+	  Notice how as a frame's status progresses, it only gains
+	  information.
+      -->
+      <frame name="distren://ohnopub.net/job/36/frame/26"
+	     server="distren://protofusion.org/"
+	     file="distren://ohnopub.net/job/36/file/2" />
+    </frames>
+
     <povray
 	ini="sphere.ini"
 	/>