ActorContext

The character that will be used in the full name definitions of the actors.

Global maximum number of letters per mailbox.

The minimal number of poll loops (from the guard) for an actor to be considered silent.

Helper method for tracing while debugging. Wrap your debug lines in traceln()

The prefix used in actor names for actors that are workers

Delayed task to be executed on the ActorContext.

Future to be executed on the ActorContext.

Default way to handle an exception. Override if needed.

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 digestible process. As longs as there is no result yet, the attempt should produce None

Indicates if the context runs on system threads or in an emulated environment.

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

Method to detect on which platform the code is running.

Plan a new task on the current Execution Context, which is run after some delay. Depending on the platform, the execution of multiple delayed tasks can hinder each other. So it is best to keep the execution time within the callable low, and transfer work to the thread pool.

Perform a shutdown request. With force=false, the shutdown will be effective if all threads have completed there current tasks. With force=true the current execution is interrupted. In any case, no new tasks will be accepted.

True if all treads have completed, for JS this is never the case since the main thread is always running. We cannot probe if the tasks there were scheduled manually all have been completed.

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

This method waits until the application finishes. Every timeout, it will probe a shutdown request. There may be other reasons for shutdown as well. After all threads have completed (by force or not) the method calls complete(). Call waitForExit in the main thread as last action there. After return some other tasks may still be running. This will usually not be a problem, since when they complete the application will exit, just as intended, or, inside a web app, keeps running, needed to be able to continue to respond on other events. The method may also directly return, if blocking is not supported by the platform (JS). In that case the callback complete provides the correct information.