JCoBox: Generalizing Active Objects to Concurrent Components

Parallel actor monitors: Disentangling task-level parallelism from data partitioning in the actor model

“…JCoBox [15] and Creol [16] introduce a generalization of active objects which enables cooperative multi-tasking within an active object. This is opposed to PAM which provides full preemptive threads inside an actor.…”

“…The executeAtomic method goes over the atomicTable and checks for each group of method patterns whether the inbox has a matching message for each of these patterns (Lines 13-18). If this is the case all these messages are executed in parallel and the executing variable is updated to keep track of the amount of messages which are being executed (Lines [15][16].…”

Analysis of Deadlocks in Object Groups

“…In particular FJg is a subcalculus of JCoBox c in [20], where the emphasis was the definition of the semantics and the type system of the calculus and the implementation in Java.…”

“…Our objectoriented language, called FJg, is an imperative version of Featherweight Java [10] with method invocations that are asynchronous and group-oriented primitives that are taken from Creol [11] (cf. the JCoBoxes [20]). …”

Multi-threaded Active Objects

“…Active objects, on the other hand, return futures [6] as placeholders for the result, allowing the invoker to continue its execution. Futures can be created and accessed either explicitly, like in Creol [7] and JCoBox [8], or implicitly as in ASP [3] (Asynchronous Sequential Processes) and AmbientTalk [9]. A key benefit of the implicit creation is that no distinction is made between synchronous (i.e., local) and asynchronous (i.e., remote) operations in the program.…”