| | 1 | = Interpreted languages: Java, Python, Perl, LISP etc. = |
| | 2 | |
| | 3 | Considered storing all details of installed languages etc with platform data of each client machine. Project will submit only to machines with adequate configurations. Not retained, as we believe each project application will have specific requirements and it will anyway be too complicated to deduce client suitability from extensive platform data. |
| | 4 | |
| | 5 | Concluded: we need BOINC feature(s) to allow the project to "probe" each client immediately before each WU execution of an interpreted app, and if necessary (re-)upload needed interpreter versions. These may be simply project files, placed in project filespace and not actually "installed". Sometimes may have to ask the user to upgrade installed version(s) and retry later. Same approaches will also work for virtual hypervisors or emulators needed for virtualized/emulated applications. |
