Combine the two behaviors such that incoming messages are distributed to both of them, each one evolving its state independently.
Combine the two behaviors such that incoming messages are distributed to both of them, each one evolving its state independently.
Process an incoming Signal and return the next behavior.
Process an incoming Signal and return the next behavior. This means that all lifecycle hooks, ReceiveTimeout, Terminated and Failed messages can initiate a behavior change.
The returned behavior can in addition to normal behaviors be one of the canned special objects:
* returning Stopped
will terminate this Behavior
* returning Same
designates to reuse the current Behavior
* returning Unhandled
keeps the same Behavior and signals that the message was not yet handled
Code calling this method should use Behavior$ canonicalize
to replace
the special objects with real Behaviors.
Process an incoming message and return the next behavior.
Process an incoming message and return the next behavior.
The returned behavior can in addition to normal behaviors be one of the canned special objects:
* returning Stopped
will terminate this Behavior
* returning Same
designates to reuse the current Behavior
* returning Unhandled
keeps the same Behavior and signals that the message was not yet handled
Code calling this method should use Behavior$ canonicalize
to replace
the special objects with real Behaviors.
Narrow the type of this Behavior, which is always a safe operation.
Narrow the type of this Behavior, which is always a safe operation. This method is necessary to implement the contravariant nature of Behavior (which cannot be expressed directly due to type inference problems).
Widen the type of this Behavior by providing a filter function that permits only a subtype of the widened set of messages.
Widen the type of this Behavior by providing a filter function that permits only a subtype of the widened set of messages.
Combine the two behaviors such that incoming messages are given first to the left behavior and are then only passed on to the right behavior if the left one returned Unhandled.
Combine the two behaviors such that incoming messages are given first to the left behavior and are then only passed on to the right behavior if the left one returned Unhandled.
(tap: BehaviorDecorators[T]).behavior
This type of Behavior wraps another Behavior while allowing you to perform some action upon each received message or signal. It is most commonly used for logging or tracing what a certain Actor does.