| | 1 | = Simplified application development = |
| | 2 | |
| | 3 | |
| | 4 | Greg Becker has an application that is seperated from the boinc framework.... using |
| | 5 | monte carlo simulation... they need more computing power ... |
| | 6 | |
| | 7 | Users get scared away by the master side programming, too complicated |
| | 8 | |
| | 9 | Kornafeld Adam: BOINC should provide an example master app, which aggregates all master side |
| | 10 | project specific functionality |
| | 11 | |
| | 12 | Figure out a a way to specify input without files, maybe JSON format ? Internaly BOINC still stores files, |
| | 13 | but the application developer would not be aware ony of them |
| | 14 | |
| | 15 | Event based ? Master-side interface so interpreted languages can use it too? lightweight so it can reimplemented in any |
| | 16 | language? |
| | 17 | |
| | 18 | Data (input file) transfer (master -> client) should be made transparent ? bindings for each language ? |
| | 19 | |
| | 20 | Cross-compiling ? Autobuilding assimilator/client/validator ? signing ? self-signing project ? |
| | 21 | cross-compiling should me avoided at all costs |
| | 22 | |
| | 23 | [ web form for scientists, where code can be copied in and gets compiled ] |
