WASM Apps are able use one thread to process callback functions instead of creating thread for each WASM app

[donghengqaz]

I'm focused on Embedded solution, so I very care about resource cost of hardware, especially RAM resource. For these installed WASM APPs whose entry is on_init, I think adding features to use one thread to process their callback functions is good choice, because in many cases these callback functions may not cause much time but creating thread for each APP costs much SRAM.

If I have more fantasy, did WAMR consider supporting co-process mode? In this mode all threads which are create in WASM APPs run and are scheduled in one single thread instead of in independent threads.