| 28 | | This design requires major server and client changes, in addition to the superhost application. A simplified design could start by treating the superhost as a project from the point of view of the clients, and as a client from the point of view of the projects. |
| | 28 | This design requires '''major''' server and client changes, in addition to the superhost application. |
| | 29 | * The scheduler RPC schema will need extending to cope with more complex requests. |
| | 30 | * The scheduler will have to treat such requests differently. |
| | 31 | * The client will have to attach to a superhost ([AccountManagement account manager] RPCs may be useful here). |
| | 32 | A simplified design could start by treating the superhost as a project from the point of view of the clients, and as a client from the point of view of the projects. Discussion on boinc_dev resulted in a consensus that this approach is impractical, since there would be so many special cases. This leaves designing the superhost as an end-to-end system. |
| | 33 | |
| | 34 | SZTAKI have a hierarchical BOINC implementation. Source should be available soon. |
