2002-07-29 19:01:38 +00:00
|
|
|
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
|
|
|
|
|
"http://www.w3.org/TR/1999/REC-html401-19991224/loose.dtd">
|
|
|
|
|
<html lang="en">
|
|
|
|
|
<head>
|
|
|
|
|
<title>Projects and Applications</title>
|
|
|
|
|
<meta name="generator" content="BBEdit 6.1.2">
|
|
|
|
|
</head>
|
|
|
|
|
<body>
|
|
|
|
|
<h2>Projects and Applications</h2> A <b>project</b> is a group of one or
|
|
|
|
|
more distributed applications, run by a single organization, that use
|
|
|
|
|
BOINC. Projects are independent; each one has its own applications,
|
|
|
|
|
databases and servers, and is not affected by the status of other
|
|
|
|
|
projects.
|
2002-04-30 22:22:54 +00:00
|
|
|
<p>
|
2002-07-29 19:01:38 +00:00
|
|
|
Each is identified by a <a href="master_url.html">master URL</a>,
|
2002-07-29 00:39:45 +00:00
|
|
|
which refers to an XHTML document describing the project.
|
2002-07-29 19:01:38 +00:00
|
|
|
</p>
|
2002-07-29 00:39:45 +00:00
|
|
|
<p>
|
2002-07-29 19:01:38 +00:00
|
|
|
Creating projects is relatively easy. An organization can create
|
|
|
|
|
projects to do Alpha and Beta testing of applications. Testers can
|
|
|
|
|
register for these projects, in addition to or instead of the
|
|
|
|
|
organization's public project.
|
|
|
|
|
</p>
|
2002-07-29 00:39:45 +00:00
|
|
|
<p>
|
2002-07-29 19:01:38 +00:00
|
|
|
The components of a project are shown below.
|
|
|
|
|
</p>
|
2002-04-30 22:22:54 +00:00
|
|
|
<br>
|
2002-07-29 19:01:38 +00:00
|
|
|
<img vspace="10" src="project.png" alt="Project Organization
|
|
|
|
|
Diagram">
|
2002-04-30 22:22:54 +00:00
|
|
|
<p>
|
2002-07-29 19:01:38 +00:00
|
|
|
The server side of a project consists of two parts:
|
|
|
|
|
</p>
|
2002-04-30 22:22:54 +00:00
|
|
|
<ul>
|
2002-07-29 19:01:38 +00:00
|
|
|
<li>
|
|
|
|
|
A <b>project back end</b> that supplies applications and work
|
|
|
|
|
units, and that handles the computational results. Input and output
|
|
|
|
|
files are distributed by <b>data servers</b>, which are HTTP servers
|
|
|
|
|
able to handle CGI programs with POST commands. These servers need not
|
|
|
|
|
be owned or operated by the project. A project might, for example,
|
|
|
|
|
recruit other organizations to donate network bandwidth by hosting data
|
|
|
|
|
servers; data could be moved on tape between the project back end and
|
|
|
|
|
the data servers.
|
|
|
|
|
</li>
|
|
|
|
|
<li>
|
|
|
|
|
A <b>BOINC server complex</b> that manages data distribution and
|
|
|
|
|
collection.
|
|
|
|
|
</li>
|
2002-04-30 22:22:54 +00:00
|
|
|
</ul>
|
2002-07-29 19:01:38 +00:00
|
|
|
The BOINC server complex includes the following components:
|
2002-04-30 22:22:54 +00:00
|
|
|
<ul>
|
2002-07-29 19:01:38 +00:00
|
|
|
<li>
|
|
|
|
|
One or more <b>scheduling servers</b> that communicates with
|
|
|
|
|
participant hosts.
|
|
|
|
|
</li>
|
|
|
|
|
<li>
|
|
|
|
|
A relational database storing information about work, results,
|
|
|
|
|
and participants.
|
|
|
|
|
</li>
|
|
|
|
|
<li>
|
|
|
|
|
Utility programs and libraries that allow the project back end
|
|
|
|
|
to interact with the server complex.
|
|
|
|
|
</li>
|
|
|
|
|
<li>
|
|
|
|
|
Web interfaces for participants and developers.
|
|
|
|
|
</li>
|
2002-04-30 22:22:54 +00:00
|
|
|
</ul>
|
2002-07-29 19:01:38 +00:00
|
|
|
</body>
|
|
|
|
|
</html>
|
