Changes between Version 2 and Version 3 of BoincLite


Ignore:
Timestamp:
Sep 18, 2010, 1:03:15 PM (14 years ago)
Author:
mo.v
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • BoincLite

    v2 v3  
    33Peter Hanappe, Sony Computer Science Laboratory
    44
    5 !BoincLite de
    6 fines the minimum API to realise a simple BOINC client.
     5!BoincLite defines the minimum API to realise a simple BOINC client.
    76Its main functionality is to download work units, to upload the results, and
    87to make sure there is always one work unit ready to be executed. It has a
    98fair number of restrictions compared to the existing BOINC manager:
    109 * It handles only one BOINC project.
    11  * It doesn't manage the resource usage (CPU, memory, disk) nor the
    12 scheduling between projects and work units. If resource management
    13 is needed, the calling application will have to implement it.
    14  * It doesn't provide any glue for constructing a user interface. Again,
    15 this has to be managed by the calling application.
    16  * Only one workunit is computed at once and at most one workunit is
    17 waiting to be executed.
    18  * The downloads and uploads are performed sequentialy.
    19  * The library doesn't use multi-threading. However, it is straighforward
    20 to spin of separate threads for the scheduler for and the computation
    21 of the work unit so that they run parallel to the main thread.
     10 * 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.
     11 * It doesn't provide any glue for constructing a user interface. Again, this has to be managed by the calling application.
     12 * Only one workunit is computed at once and at most one workunit is waiting to be executed.
     13 * The downloads and uploads are performed sequentially.
     14 * 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.
    2215
    2316The library consists of four components: !BoincScheduler, !BoincProxy,
    24 !BoincCon
    25 guration, and !BoincHttp (see Fig. ).
     17!BoincConfiguration, and !BoincHttp (see Fig. ).
    2618
    2719!BoincHttp is a thin abstraction layer for handling HTTP requests. It is
     
    2921HTTP libraries, such as libcurl on Linux or libhttp on CellOS.
    3022
    31 The !BoincCon
    32 guration is another shallow abstraction layer. It man-
    33 ages all the confi
    34 guration data needed by BOINC, such as the user ID, the
    35 authenticator string, but also the disk usage or the FLOPS of the host machine.
     23The !BoincConfiguration is another shallow abstraction layer. It manages all the configuration data needed by BOINC, such as the user ID, the
     24authenticator string, and also the disk usage or the FLOPS of the host machine.
    3625
    3726!BoincLite source code and documentation are here: