2004-06-09 19:09:16 +00:00
|
|
|
<?php
|
2003-08-19 06:44:58 +00:00
|
|
|
require_once("docutil.php");
|
|
|
|
page_head("Versions of BOINC");
|
|
|
|
echo "
|
2002-12-01 06:14:28 +00:00
|
|
|
|
|
|
|
<p>
|
2004-11-29 22:26:34 +00:00
|
|
|
The BOINC software (including client and server components)
|
|
|
|
evolve over time.
|
2002-12-01 06:14:28 +00:00
|
|
|
There are a number of pairwise interactions
|
|
|
|
in which version mismatches could cause problems:
|
|
|
|
<ul>
|
|
|
|
<li> RPC from core client to scheduling server.
|
|
|
|
<li> RPC from core client to file upload handler.
|
2004-11-29 22:26:34 +00:00
|
|
|
<li> Interface between core client and application.
|
2002-12-01 06:14:28 +00:00
|
|
|
<li> Interface between BOINC DB and all BOINC back-end components.
|
|
|
|
<li> The parsing of the core state file by the core client.
|
|
|
|
</ul>
|
|
|
|
|
|
|
|
<p>
|
2005-08-31 00:18:36 +00:00
|
|
|
Each BOINC software component has a version
|
|
|
|
consisting of three integers:
|
|
|
|
major, minor, and release.
|
2002-12-01 06:14:28 +00:00
|
|
|
|
|
|
|
<p>
|
|
|
|
When a participant updates the core client,
|
|
|
|
all results currently in progress are discarded
|
|
|
|
(because new app versions would be needed).
|
|
|
|
The core client reads the version number from the old
|
|
|
|
client state file, and discards the results.
|
|
|
|
|
|
|
|
<p>
|
2004-11-29 22:26:34 +00:00
|
|
|
Some changes to the BOINC server software may involve
|
|
|
|
changes to the BOINC database
|
|
|
|
(e.g. adding a new table or field).
|
|
|
|
Such releases will include SQL script for modifying an
|
|
|
|
existing database in-place.
|
|
|
|
|
2003-08-19 06:44:58 +00:00
|
|
|
";
|
|
|
|
page_tail();
|
|
|
|
?>
|