| 21 | | This system is coupled with BOINC's [MultiUser multi-user project features]. |
| 22 | | This includes access control: |
| 23 | | users can submit jobs only if they have been given access by project administrators, |
| 24 | | and admins can restrict the apps for which each user is allowed to submit jobs. |
| | 21 | Notes: |
| | 22 | |
| | 23 | * This system is coupled with BOINC's [MultiUser multi-user project features], |
| | 24 | which include access control: |
| | 25 | users can submit jobs only if they have been given access by project administrators, |
| | 26 | and admins can restrict the apps for which each user is allowed to submit jobs. |
| | 27 | * Input files must be accessible via HTTP; they are downloaded by the BOINC server |
| | 28 | during job submission. |
| | 29 | * As jobs are completed, their output files are available to the submitting user via HTTP. |
| | 30 | When a batch is complete, a zipped archive of all its output files is available |
| | 31 | via HTTP. |