From 4ca5635fde6bd7db7c5bc625bc5ddd9bd1fd1d5d Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Johan=20Andr=C3=A9n?= Date: Mon, 8 Aug 2016 12:52:25 +0200 Subject: [PATCH] Don't mention akka.udp as a remote transport to use in the docs #21112 --- akka-docs/rst/general/addressing.rst | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/akka-docs/rst/general/addressing.rst b/akka-docs/rst/general/addressing.rst index 0768dc82b4..9edbe6297d 100644 --- a/akka-docs/rst/general/addressing.rst +++ b/akka-docs/rst/general/addressing.rst @@ -107,8 +107,8 @@ actors in the hierarchy from the root up. Examples are:: "akka://my-sys/user/service-a/worker1" // purely local "akka.tcp://my-sys@host.example.com:5678/user/service-b" // remote -Here, ``akka.tcp`` is the default remote transport for the 2.2 release; other transports -are pluggable. A remote host using UDP would be accessible by using ``akka.udp``. +Here, ``akka.tcp`` is the default remote transport for the 2.4 release; other transports +are pluggable. The interpretation of the host and port part (i.e. ``host.example.com:5678`` in the example) depends on the transport mechanism used, but it must abide by the URI structural rules.