DistRen Changeset - 681c2fb8e6a3 · protofusion repositories

Changeset - 681c2fb8e6a3

Parent rev.

Child rev.

[Not reviewed]

default

0 1 0

ethanzonca - 16 years ago 2009-07-23 01:08:05

XML commenting, please add XML to buildenv
Also, usefulness of XML to lessen client/server communication, including some rambling.

1 file changed with 23 insertions and 0 deletions:

src/server/distrend.c

0 comments (0 inline, 0 general)

src/server/distrend.c

➞

Show inline comments

@@ @@ -6,48 +6,71 @@ @@
   DistRen is free software: you can redistribute it and/or modify
   it under the terms of the GNU Affero General Public License as published by
   the Free Software Foundation, either version 3 of the License, or
   (at your option) any later version.
   DistRen is distributed in the hope that it will be useful,
   but WITHOUT ANY WARRANTY; without even the implied warranty of
   MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
   GNU Affero General Public License for more details.
   You should have received a copy of the GNU Affero General Public License
   along with DistRen.  If not, see <http://www.gnu.org/licenses/>.
 */
 /* This file contains the code which both processes (renders) jobs as a slave, and the code which distributes frames to slaves after receiving them from the client portion of the codebase. */
  /* Just some notes -- Ethan Zonca
  * ++ Make data availible for other apps to parse
  * Server<==>Client Communication
  * Upload while rendering
  */
 /* XML notes --
+ *
  * First off, is XML in our build environment?
  * Next, what files are we going to have?:
  * 	- XML file sent with (.blend/.pov/.lux(xml)/whatever) telling what to do
  * 		+ Will this take care of some client/server communication?
  *  - XML file on server storing info on current and finished jobs
  *  - XML file sent by distren when submitting a render to the server
  *  	+ Includes submitter name, filename, emailaddress, etc
+ *
  *  Overall, we could use XML to make our client/server communication load
  *  a lot lighter, especially if clients are sent customized xml files telling
  *  them what frame(s) to render... although that would be inefficient if rendering
  *  single frames. Maybe not tell it what frames to render in the xml file, the server
  *  can spit out that info.
+ *
  *  Please edit my ramblings if you please,
  *  --ethanzonca
+ *
  */
 #include "execio.h"
 #include "options.h"
 #include <confuse.h>
 #include <stdio.h>
 #include <stdlib.h>
 #include <malloc.h>
 #include <unistd.h> /* getopt */
 #include <time.h>
 typedef unsigned int jobnum_t;
 /* ******************* Structs ************************ */
 // Stores config info? editmycomment
 struct distrend_config
+{
   cfg_t *mycfg;
   struct options_common *options;
   struct distrend_listen **listens; /*< Null terminated array of structs */
 };

0 comments (0 inline, 0 general)