| | 1 | == Possible extensions == |
| | 2 | === Integration with BOINC === |
| | 3 | |
| | 4 | Some offline jobs may involve computation done through BOINC; |
| | 5 | i.e. if the job is assigned to a team, the computation is queued |
| | 6 | in the project's BOINC server and dispatched to members of the team. |
| | 7 | (Or if the job is assigned to a user with many computers, |
| | 8 | those computers are used). |
| | 9 | |
| | 10 | * Tasks may be short (performed online via a single web page) or may take several weeks and involve running separate programs. |
| | 11 | * Tasks may be performed by a single user or by a group of cooperating users. |
| | 12 | * Tasks may be unvalidated, automatically validated, or validated by comparing redundant instances. |
| | 13 | |
| | 14 | === Teams as volunteers === |
| | 15 | Each job instance is assigned either to a user or to a team. |
| | 16 | |
| | 17 | === Offline jobs |
| | 18 | * Offline: jobs are not online, e.g. because they're potentially handled by a group of users, or requires other asynchronous activity. |
| | 19 | |
| | 20 | A project can configure: |
| | 21 | |
| | 22 | * A maximum number of outstanding offline jobs per user or group |
| | 23 | * A maximum number of jobs per day issued per user or group |
