Prax hangs forever with concurrent requests to an app while it spawns about prax.cr HOT 2 CLOSED

This can't be solved without implementing #11 (have communicating actors).

from prax.cr.

The reason we have mutexes in Prax is to avoid concurrent spawns of the rack/shell applications. Starting an application may take many seconds, so concurrent requests may come in, telling Prax to start the same application... which is undefined behavior.

With a mutex we could synchronize the start and stop actions to never be invoked concurrently, while having other threads waiting for the application to either start or stop or fail to start, so we could reply adequately. Perfect.

But this broke since we replaced threads for an event-loop (coroutines) since they run on a single thread, and running mutex.synchronize a second time from the same thread... will lock the thread forever. Bummer.

AFAIK there are no equivalent to mutexes for coroutines, so we must either: implement an equivalent to Mutex#synchronize for coroutines, or we should implement #11 to fix this bug correctly.

from prax.cr.