Pending for capataz.
- Controlled repetition strategies, e.g.: repeat until 2 agree, repeat and select or average, etc.
- Proper testing with browsers (maybe with Karma).
- Benchmarking of memory use.
- Random delay for
Drudger
initialization, to prevent server overload. - Better control with brief console commands (i.e.
APP
methods). - Worker count report and control in the web page.
- Statistic report page with autorefresh.
- Test using of GPU.js.
- Test using WebDAV repositories of data.
- Job data attached to job's future. E.g. in
scheduleAll
the callback cannot use the data used to generate the job in the iterator.