Specific code fails to port to HTML5, Flash about haxe-concurrent HOT 3 CLOSED

HTLM and Flash targets are single threaded. So your loop

		do {
			trace(done.toString());
		} while (!result.isComplete());

blocks any potential async execution.

Depending on the target platform a different Executor implementation is selected:

For HTML/Flash it is the TimerExecutor which uses haxe.Timer to schedule async execution of code. As long as you have actively running any code the execution of any scheduled async tasks is prevented.

To get true parallelism on the web one would need to use webworkers, however this has other consequences as they cannot access shared state but run in isolated processes.

from haxe-concurrent.

Out of curiosity, how can i wait or tell if all of the submissions in the TimerExecutor or ThreadPoolExecutor is completed? How would i fix the do while loop to not block any async execution?

from haxe-concurrent.

You need to get all your code after executor.submit(...) out of the event loop to allow the browser/flash to do event processing.
This means you need to work with callbacks. Something like:

  trace("waiting...");
  var resultFuture = executor.submit(task);
  result.onCompletion(result => {
    // your code...
  });

For HTML or Flash using the Executor will not improve performance as still only a single thread (the event loop) running on a single core is used. This is a target specific limitation. To do parallelism in Browser/HTML you could play around with webworkers but as I said this does not work with shared states and involves serialization/message passing.

from haxe-concurrent.