The binary plugin runner solution was implemented assuming that a (binary) plugin will only run once on the host machine, with one input to be scanned and one result to produce. This will not be the case after merging this, so it will need some refactoring to ensure these binary plugin scanners can run in parallel.
Plugin binary approach doesnt need to be optimized for multi-input scan, but rather be safe to call/work with multi-input scans. Hope this clarifies it
The binary plugin runner solution was implemented assuming that a (binary) plugin will only run once on the host machine, with one input to be scanned and one result to produce. This will not be the case after merging this, so it will need some refactoring to ensure these binary plugin scanners can run in parallel.
This issue also belongs to this problem.