DistRen Changeset - 12246b166181 · protofusion repositories

Changeset - 12246b166181

Parent rev.

Child rev.

[Not reviewed]

default

0 2 0

Nathan Brink (binki) - 15 years ago 2010-08-08 00:19:54
ohnobinki@ohnopublishing.net

Provide a basic model for job distribution.

2 files changed with 12 insertions and 1 deletions:

doc/architecture.txt

doc/distrenjob.xml.example

0 comments (0 inline, 0 general)

doc/architecture.txt

➞

Show inline comments

@@ @@ -26,12 +26,17 @@ Concepts: @@
       arbitrary data storage out of the box. This should allow different rendering backends to
       store the extra information that is specific to that backend.
   - post-render rebundling: Again, to make things simpler, the server where a job is rendered
       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
       frame's identification number would be useless without an accompanying job identifier. The
       numeric value of a frame identification value must be unique to that job. There are no
       restrictions of ordering of frame numbers except that they are not to be negative. There

doc/distrenjob.xml.example

➞

Show inline comments

@@ @@ -41,13 +41,19 @@ @@
        width="800"
        height="600"
        />
     <!--
 	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" />
       <!--
 	  As described in architecture.txt, we allow frame

0 comments (0 inline, 0 general)