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. |
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. |
| 23 | The !BoincConfiguration is another shallow abstraction layer. It manages all the configuration data needed by BOINC, such as the user ID, the |
| 24 | authenticator string, and also the disk usage or the FLOPS of the host machine. |