Files
@ 2d956d549430
Branch filter:
Location: DistRen/doc/distrenjob.xml.example
2d956d549430
3.5 KiB
text/plain
Add simple CSV parser for normaldotcom.
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 | <?xml version="1.0" encoding="utf-8" ?>
<!--
Copyright 2009 Nathan Phillip Brink, Ethan Zonca, Matthew Orlando
This file is a part of DistRen.
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/>.
-->
<distren>
<!-- is the priority option actually useful? -->
<job
name="distren://ohnopub.net/job/36"
submitter="distren://ohnopub.net/user/binki"
type="povray"
>
<!--
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. 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. 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
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"
/>
</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>
<user
name="normaldotcom"
href="http://ohnopublishing.net/~ohnobinki/"
/>
</submitters>
</distren>
|