Merge pull request #22261 from toaditoad/issue-22256-artery-docs-msg-destination

Documentation hint for large-message-destinations
This commit is contained in:
Patrik Nordwall 2017-02-05 19:11:35 -07:00 committed by GitHub
commit d06fd8a50f
3 changed files with 3 additions and 2 deletions

View file

@ -529,7 +529,7 @@ helpful to separate actors that have different QoS requirements: large messages
Akka remoting provides a dedicated channel for large messages if configured. Since actor message ordering must
not be violated the channel is actually dedicated for *actors* instead of messages, to ensure all of the messages
arrive in send order. It is possible to assign actors on given paths to use this dedicated channel by using
path patterns::
path patterns that have to be specified in the actor system's configuration on both the sending and the receiving side::
akka.remote.artery.large-message-destinations = [
"/user/largeMessageActor",

View file

@ -529,7 +529,7 @@ helpful to separate actors that have different QoS requirements: large messages
Akka remoting provides a dedicated channel for large messages if configured. Since actor message ordering must
not be violated the channel is actually dedicated for *actors* instead of messages, to ensure all of the messages
arrive in send order. It is possible to assign actors on given paths to use this dedicated channel by using
path patterns::
path patterns that have to be specified in the actor system's configuration on both the sending and the receiving side::
akka.remote.artery.large-message-destinations = [
"/user/largeMessageActor",

View file

@ -744,6 +744,7 @@ akka {
# "/user/supervisor/actor/*" will match any direct child to actor,
# while "/supervisor/*/child" will match any grandchild to "supervisor" that
# has the name "child"
# Entries have to be specified on both the sending and receiving side.
# Messages sent to ActorSelections will not be passed through the large message
# stream, to pass such messages through the large message stream the selections
# but must be resolved to ActorRefs first.