-S <name> Set scene <name>

  -f <frame> Render frame <frame> and save it

  -s <frame> Set start frame (use before -a argument)

  -e <frame> Set end frame (use before -a argument>

  -o <path> Set the render path and file name (use // at start of the path to render relative to the blend file, the ### characters are replaced by the frame number)

  -t <threads> Use amount of ,threads> for rendering (background mode only)(1-8, 0 for systems processor count)

  -x <bool> Set option to add the file extension to the end of the file

*/

#include <stdio.h>

/* Just some notes -- Ethan Zonca

 *

 * So I read the IRC transcript, and we need some communication and plugin (e.g., blender, povray) standards.

 * In addition to those standards, we should also have standards for information availability,

 * making statistics and remote control of each plugin or the whole system standard and common,

 * so other apps can grab stats from it (such as a j2me phone DistRen status app or a php web

 * interface).

 *

 *

 *

 * Notes from IRCness:

 * Server<==>Client Communication

 *

 *  blender_getframecount()

 *  indigo_getframecount() always return 1... or just not bother with it?

 *

 *

 *

 */

// Let's fix those global variable issues one of these days! :D test

int main(int argc, char *argv[])

{

  return 0;

}

struct blender_job_server // will be stored and edited in the blender_job_que

{

	char file_name[25];

	int start_frame;

	int end_frame;

};

struct blender_job_client // will be sent to the client

{