Interface Scope

All Known Implementing Classes:
ClusterScope, ClusterScope$, LocalScope, LocalScope$, NoScopeGiven, NoScopeGiven$, RemoteScope

public interface Scope
The scope of a pekko.actor.Deploy serves two purposes: as a marker for pattern matching the “scope” (i.e. local/remote/cluster) as well as for extending the information carried by the final Deploy class. Scopes can be used in conjunction with a custom pekko.actor.ActorRefProvider, making Pekko actors fully extensible.
  • Method Summary

    Modifier and Type
    Method
    Description
    When merging pekko.actor.Deploy instances using withFallback() on the left one, this is propagated to “merging” scopes in the same way.
  • Method Details

    • withFallback

      Scope withFallback(Scope other)
      When merging pekko.actor.Deploy instances using withFallback() on the left one, this is propagated to “merging” scopes in the same way. The setup is biased towards preferring the callee over the argument, i.e. a.withFallback(b) is called expecting that a should in general take precedence.