2002-09-05 11:46:10 +00:00
|
|
|
<title>The master URL</title>
|
2002-08-20 23:54:17 +00:00
|
|
|
<body bgcolor=ffffff>
|
2002-09-05 11:46:10 +00:00
|
|
|
<h2>The master URL</h2>
|
2002-07-05 05:33:40 +00:00
|
|
|
<p>
|
2002-08-19 18:43:10 +00:00
|
|
|
Each project is identified by a <b>master URL</b>.
|
|
|
|
|
This URL is used to publicize the project.
|
|
|
|
|
The <b>master page</b> at this URL has two functions.
|
2002-07-05 05:33:40 +00:00
|
|
|
<ul>
|
2002-08-19 18:43:10 +00:00
|
|
|
<li> It is the home page of the project; when viewed in a browser it
|
2002-07-29 19:01:38 +00:00
|
|
|
describes the project and contains links for registering and for
|
|
|
|
|
downloading the core client.
|
2002-08-19 18:43:10 +00:00
|
|
|
<li> It contains XML tags of the form <pre>
|
2002-07-29 19:01:38 +00:00
|
|
|
<scheduler>http://host.domain.edu/cgi/scheduler<scheduler>
|
|
|
|
|
<scheduler>http://host2.domain.edu/cgi/scheduler<scheduler>
|
2002-08-19 18:43:10 +00:00
|
|
|
</pre>
|
|
|
|
|
that give the URLs of the project's scheduling servers.
|
|
|
|
|
These tags can be embedded within HTML comments.
|
|
|
|
|
The BOINC core client reads
|
|
|
|
|
and parses the master page to find scheduler servers.
|
|
|
|
|
If it is unable to
|
|
|
|
|
connect to any scheduler server for a project, it rereads the master page.
|
2002-07-05 05:33:40 +00:00
|
|
|
</ul>
|
2002-07-29 19:01:38 +00:00
|
|
|
This mechanism lets a project change the locations of its scheduling
|
|
|
|
|
servers, or add new servers.
|
