- job: Represents a collection of renderings that must be unbundled, rendered, and bundled together again.

  - job identification: A server shall internally assign numeric job identifiers. It must only

      make sure that it never issues the same numeric job identifier to multiple jobs. To allow

      multiple servers to share jobs with eachother (which is the the whole point of distren),

      a job shall be refered to by prefixing the job a server identification. For example,

  - job packaging: Currently, the most creative way of dealing with jobs I have at the moment is

      storing all of the data necessary to render the job in a tarball. This tarball can be

      treated as a directory of a normal filesystem. A job's directory would contain at least one

      file called ``distrenjob.xml'' which provides information necessary to render the job. This

      will be an XML file rather than a rigidly defined binary format because XML supports

      arbitrary data storage out of the box. This should allow different rendering backends to

- 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

      need be no sequencing of frame numbers either. Thus, a frame identification URL would look

  - size: A frame hopefully represents a smaller unit of work in terms of the rendering

      back-end's capabilities. For example, POV-Ray's CLI can initiate and carry out the rendering

      of an entire animation. But distren would hopefully be able to provide a clean method for

      rendering each individual frame and bringing the resulting set of files back to the user

      in a much shorter time than a single computer could on its own. Many smaller and distinct

      is key to a project being benefited by distren.

      jobs registered in a server.

  - servers: A server, though having many more functions, shall be able to also perform the list

      of actions a client may perform.

- user: A user is an entity which is given access to a distren server.

  - user identifiction: As users are per-server, a user shall be identified by the name of the

- file: There are different uses of files above and distributed rendering requires file distribution.

  - file identification: Every file mentioned above was at least in the context of a job. Thus,

      file identification numbers shall be assigned in the context of a job identification number.

      They shall, however, be numeric.

  along with DistRen.  If not, see <http://www.gnu.org/licenses/>.

-->

<distren>

  <!-- is the priority option actually useful? -->

  <job

     >

    <resolution

       width="800"

       height="600"

       />

  </job>

  <!--

      Additional section:

      The contents of this section should probably be

      moved to some central store, as it will be referenced

      in multiple jobs.

    -->

  <submitters>

       name="normaldotcom"

       href="http://ohnopublishing.net/~ohnobinki/"

       />

  </submitters>

</distren>