Skip to content

Commit 3e9f3c7

Browse files
committed
Add Netty links
1 parent 03f2af7 commit 3e9f3c7

File tree

1 file changed

+3
-3
lines changed

1 file changed

+3
-3
lines changed

docs/internal/GeneralArchitectureGuide.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -54,8 +54,8 @@ that require [operator privileges], populate the [audit logs] and perform some a
5454
HTTP traffic is handled by an implementation of a [HttpServerTransport]. The `HttpServerTransport` is responsible for binding to a
5555
port, handling REST client connections, parsing received requests into [RestRequest] instances and dispatching those
5656
requests to a [HttpServerTransport.Dispatcher]. The [RestController] is an implementation of `HttpServerTransport.Dispatcher`.
57-
The `HttpServerTransport` is pluggable. There is only a single [Netty-based implementation][Netty4HttpServerTransport]
58-
of `HttpServerTransport`, but some plugins, such as `Security`, supply instances of it with
57+
The `HttpServerTransport` is pluggable. There is a single [Netty](https://netty.io/)-based implementation
58+
of `HttpServerTransport`, the [Netty4HttpServerTransport], but some plugins, such as `Security`, supply instances of it with
5959
additional configuration to implement features like IP filtering or TLS (see [Security#getHttpTransports]).
6060

6161
[ActionModule#initRestHandlers]:https://github.com/elastic/elasticsearch/blob/v9.0.1/server/src/main/java/org/elasticsearch/action/ActionModule.java#L814
@@ -151,7 +151,7 @@ to register interceptors by implementing the [getTransportInterceptors][NetworkP
151151

152152
The transport infrastructure is pluggable and implementations can be provided by [NetworkPlugin#getTransports]. The role of the [Transport]
153153
is to establish connections between nodes over which [TransportRequest]s can be sent, maintain a registry of [TransportRequestHandler]s for
154-
routing inbound requests and maintain state to correlate inbound responses with the original requests. There is a single Netty-based TCP
154+
routing inbound requests and maintain state to correlate inbound responses with the original requests. There is a single [Netty](https://netty.io/)-based TCP
155155
transport used in production Elasticsearch, the [Netty4Transport], but the security plugin extends that to add SSL and IP filtering
156156
capabilities.
157157

0 commit comments

Comments
 (0)