ContextImplementation

True as long as there has been no Shutdown request.

Place a task on the Execution Context which is executed after some event arrives. When it arrives it may produce an result of some type. This result is subsequently passed to the digestable process. As longs as there is no result yet, the attempt should produce None

Execute a new task on the current Execution Context directly

Returns the platform that is currentluy running, here Native.

Plan a new task on the current Execution Context, which is run after some delay.

Perform a shutdown request. With force=false, the shutdown will be effective if all threads have completed there current thasks. With force=true the current execution is interrupted. In any case, no new tasks will be accepted. Once you have called shutdown, it is no longer possible to restart the mainloop.

True if all treads have completed, for the current Native this is never the case since the main has stopped if you could get true, but you can only read this from main tread.

This method enters an endless loop until the application finishes. Every timeout, it will probe a shutdownrequest. There may be other reasons for shutdown as well. After all threads have completed (by force or not) the method calls complete() and returns. Call in the main thread as last action there. In Native it this also starts the mainloop. Normally you only call this once, but in certain situations (tests) it may be needed to call it multible times. In that case, make sure shutdownRequest is always false.

The natural pause time for this context. Its meaning and use is platform dependant.

The average thread load per core. Override to change. This is only used on multithreaded platforms.