| 21 | | * Data model: in the BOINC model, files have both logical and physical names. |
| 22 | | Physical names are unique within a project, |
| 23 | | and the file associated with a given physical name is immutable. |
| 24 | | Files may be used by many jobs. |
| 25 | | In Condor, a file is associated with a job, and has a single name. |
| | 21 | * Data model: |
| | 22 | * In BOINC, files have both logical and physical names. |
| | 23 | Physical names are unique within a project, |
| | 24 | and the file associated with a given physical name is immutable. |
| | 25 | Files may be used by many jobs. |
| | 26 | In Condor, a file is associated with a job, and has a single name. |
| | 27 | * BOINC is designed for apps that have a fixed, predetermined number of |
| | 28 | input and output files; Condor doesn't have this restriction. |
