doc edits

svn path=/trunk/boinc/; revision=374
This commit is contained in:
Eric Heien 2002-08-23 19:22:17 +00:00
parent 5fce72eebb
commit c50a827b0f
5 changed files with 40 additions and 32 deletions

View File

@ -5,21 +5,26 @@
The key data structures in the core client are as follows.
<p>
Basic types:
<pre>
PROJECT
APP
FILE_INFO
APP_VERSION
IO_FILE_DESC
WORKUNIT
RESULT
</pre>
<pre>ACCOUNTS</pre> Contains a vector of PROJECTs, summarizing
the accounts file.
<p>
<pre>PROJECT</pre>
<pre>APP</pre>
<pre>FILE_INFO</pre>
<pre>APP_VERSION</pre>
<pre>IO_FILE_DESC</pre>
<pre>WORKUNIT</pre>
Contains execution information about workunit including
command line arguments, environment variables and required
input files. Also points to the application, app
version and project the workunit is associated with.
<pre>RESULT</pre>
Contains status information about result including
state, total CPU time, deadline, etc. Also points
to the workunit, application and project the result is
associated with.
<pre>PREFS</pre>
Contains a vector of PROJECTs, summarizing the prefs.xml
file. Also contains user preferences.
<pre>CLIENT_STATE</pre>
<p>
Contains vectors of all the basic types. These are crossed-linked
with pointers; for example, APP_VERSION has a pointer to FILE_INFO. Also
contains FSM sets for network connections, HTTP operations, file
transfers, and active tasks.
transfers, persistent file transfers, and active tasks.

View File

@ -30,26 +30,22 @@ the application sees the slot directory as the root of its filesystem,
and cannot create or access files outside of it.
<p>
A participant's accounts are described in an <b>account file</b>
A participant's accounts are described in a <b>preferences file</b>
on each of their hosts.
This file looks like this:
<pre>
&lt;accounts>
&lt;preferences>
&lt;prefs_mod_time>1030128387&lt;/prefs_mod_time>
&lt;from_project>http://www.myproject.com/&lt;/from_project>
&lt;from_scheduler>http://server3.myproject.com/cgi-bin/scheduler_cgi&lt;/from_scheduler>
&lt;mod_time>2&lt;/mod_time>
&lt;high_water_days>2&lt;/high_water_days>
&lt;low_water_days>1&lt;/low_water_days>
&lt;resource_share>1&lt;/resource_share>
&lt;project>
&lt;home_project/>
&lt;domain>setiathome.berkeley.edu&lt;/domain>
&lt;scheduler_url>http://setiathome.berkeley.edu/boinc-cgi/cgi&lt;/scheduler_url>
&lt;master_url>http://www.myproject.com/&lt;/master_url>
&lt;authenticator>3f7b90793a0175ad0bda68684e8bd136&lt;/authenticator>
&lt;/project>
&lt;project>
&lt;domain>bio.wwu.edu&lt;/domain>
&lt;scheduler_url>http://bio.wwu.edu/boinc-cgi/cgi&lt;/scheduler_url>
&lt;authenticator>3f7b90793a0175ad0bda68684e8bd136&lt;/authenticator>
&lt;/project>
&lt;/accounts>
&lt;/preferences>
</pre>
<p>
One account can be designated as the <b>home project</b>;
this is the project where the user maintains their preferences.

View File

@ -32,7 +32,7 @@ It can refer to the user name, CPU time etc. obtained from
<p>
Applications that don't do graphics must also supply a
dummy <tt>app_render</tt> to link with the API.
<tt>boinc_draw_gl</tt> is called to draw grpahics
<tt>boinc_draw_gl</tt> is called to draw graphics
<hr>
<h3>Implementation</h3>

7
doc/pers_file_xfer.html Normal file
View File

@ -0,0 +1,7 @@
<title>Persistent File Transfer</title>
<body bgcolor=ffffff>
<h2>Persistent File Transfer</h2>
<p>
Since BOINC may deal with uploading or downloading very large
files, or servers which are not always available, the notion
of a persistent file transfer is necessary.

View File

@ -8,8 +8,8 @@ boinc/
api/
apps/
client/
win/
mac/
win/
mac/
db/
doc/
html_ops/