Changes between Version 2 and Version 3 of BoincLite

Timestamp:

Sep 18, 2010, 1:03:15 PM (15 years ago)

Author:

mo.v

Comment:

--

BoincLite

@@ -3 +3 @@
 Peter Hanappe, Sony Computer Science Laboratory
 
-!BoincLite de
-fines the minimum API to realise a simple BOINC client.
+!BoincLite defines the minimum API to realise a simple BOINC client.
 Its main functionality is to download work units, to upload the results, and
 to make sure there is always one work unit ready to be executed. It has a
 fair number of restrictions compared to the existing BOINC manager:
  * It handles only one BOINC project.
- * It doesn't manage the resource usage (CPU, memory, disk) nor the
-scheduling between projects and work units. If resource management
-is needed, the calling application will have to implement it.
- * It doesn't provide any glue for constructing a user interface. Again,
-this has to be managed by the calling application.
- * Only one workunit is computed at once and at most one workunit is
-waiting to be executed.
- * The downloads and uploads are performed sequentialy.
- * The library doesn't use multi-threading. However, it is straighforward
-to spin of separate threads for the scheduler for and the computation
-of the work unit so that they run parallel to the main thread.
+ * It doesn't manage the resource usage (CPU, memory, disk) nor the scheduling between projects and work units. If resource management is needed, the calling application will have to implement it.
+ * It doesn't provide any glue for constructing a user interface. Again, this has to be managed by the calling application.
+ * Only one workunit is computed at once and at most one workunit is waiting to be executed.
+ * The downloads and uploads are performed sequentially.
+ * The library doesn't use multi-threading. However, it is straighforward to spin off separate threads for the scheduler and the computation of the work unit so that they run parallel to the main thread.
 
 The library consists of four components: !BoincScheduler, !BoincProxy,
-!BoincCon
-guration, and !BoincHttp (see Fig. ).
+!BoincConfiguration, and !BoincHttp (see Fig. ).
 
 !BoincHttp is a thin abstraction layer for handling HTTP requests. It is
@@ -29 +21 @@
 HTTP libraries, such as libcurl on Linux or libhttp on CellOS.
 
-The !BoincCon
-guration is another shallow abstraction layer. It man-
-ages all the confi
-guration data needed by BOINC, such as the user ID, the
-authenticator string, but also the disk usage or the FLOPS of the host machine.
+The !BoincConfiguration is another shallow abstraction layer. It manages all the configuration data needed by BOINC, such as the user ID, the
+authenticator string, and also the disk usage or the FLOPS of the host machine.
 
 !BoincLite source code and documentation are here: