| 55 | | == Possible extensions == |
| 56 | | === Integration with BOINC === |
| 57 | | |
| 58 | | Some offline jobs may involve computation done through BOINC; |
| 59 | | i.e. if the job is assigned to a team, the computation is queued |
| 60 | | in the project's BOINC server and dispatched to members of the team. |
| 61 | | (Or if the job is assigned to a user with many computers, |
| 62 | | those computers are used). |
| 63 | | |
| 64 | | * Tasks may be short (performed online via a single web page) or may take several weeks and involve running separate programs. |
| 65 | | * Tasks may be performed by a single user or by a group of cooperating users. |
| 66 | | * Tasks may be unvalidated, automatically validated, or validated by comparing redundant instances. |
| 67 | | |
| 68 | | === Teams as volunteers === |
| 69 | | Each job instance is assigned either to a user or to a team. |
| 70 | | |
| 71 | | === Offline jobs |
| 72 | | * Offline: jobs are not online, e.g. because they're potentially handled by a group of users, or requires other asynchronous activity. |
| 73 | | |
| 74 | | A project can configure: |
| 75 | | |
| 76 | | * A maximum number of outstanding offline jobs per user or group |
| 77 | | * A maximum number of jobs per day issued per user or group |
