new methods that block the entry of an object. Implemented on machines to avoid receiving to signals at the same simulation time

Machine now communicates with Broker via events. Machine waits for isRequested signal to getEntity. Can also get an entity after a loadOperatorAvailable event in case it could not getEntity due to resources lack

new CoreObject method initialSignalReceiver. Invoked as the generator of the objects starts and control if there is WIP assigned to them and signals receivers

ObjectInterruption interrupts or signals the victim according to the state of the victim (waitToDispose)

Machine updated to conform with previous changes. Interruption handling performed by 2 new methods (interruptionActions, postInterruptionActions). canAccept&IsRequested controls also weather the exit of the giver is assigned to self (exitAssignedToReceiver) which can be updated either by signalGiver of the successor or by signalReceiver of self

Queue now waits for two types of events (isRequested, canDispose) and performs the requested actions (getEntity, signalReceiver respectively). removeEntity method also invokes signalGiver.

new process object EntityGenerator added to the module of the Source. The new process created undistructed the entities while the Source waits till successor is available to signal him in acknowledge

Exit now waits for events triggered by the giver. canAcceptAndIsRequested on control the giver, which is choosen by the method selectReceiver used by the signaling method signalReceiver

CoreObject now has three types of events for communition purposes. These are used by the methods signalReceiver/Giver. exitAssignedToReceiveris no more Boolean but holds the receiver the exit is currently assigned to

Router may assign the same candidateReceiver to candidateOperators, the sorting rule of the Queues prevail

new flag added to Router, used to check if the Router should sort the operators and the pendingEntities