the Scala system can communicate with any remote Erlang process using either direct process reference (pid) or abstarct name (aka akka path) The direct reference is type of OtpErlangPid, the abstract name is tuple of (String, String).
the Scala system can communicate with any remote Erlang process using either direct process reference (pid) or abstarct name (aka akka path) The direct reference is type of OtpErlangPid, the abstract name is tuple of (String, String). The wired data are tuples, and the tuple structure is application protocol outside of scarl implementation (it is a messanger)
The library uses concept of Envelope to express communication intent. Envelop contains the destination address and message. The union type is required to model the message destination [OtpErlangPid or (String, String)] The Curry-Howard isomorphism is elegant solution on union type https://issues.scala-lang.org/browse/SI-3749 http://milessabin.com/blog/2011/06/09/scala-union-types-curry-howard/
start scarl application, create default node with give name.
start scarl application, create default node with give name. it returns reference to root supervisor
default node name
distribution listener interface specification
bind actor to external mailbox on defined node
bind actor to external mailbox on defined node
node name
mbox unique mailbox name
either ref to existed actor of lambda expression
implicit reference to actor system
bind actor to external mailbox on default node
bind actor to external mailbox on default node
unique mailbox name, the name is used as process address to send a message
either ref to existed actor of lambda expression
implicit reference to actor system
build envelop
build envelop
either OptErlangPid or (String, String) process identity
destination address
communication message
spawn new node on existing interface
spawn new node on existing interface
locally unique node name
implicit reference to actor system
application id