From 3d98a0f47f08db76948cdfbc2606679bd22c37d6 Mon Sep 17 00:00:00 2001 From: Norman Maurer Date: Wed, 12 Jun 2024 14:37:29 +0200 Subject: [PATCH] Fix formating --- news/2024-06-12-4-2-0-Alpha1.md | 8 +++++--- 1 file changed, 5 insertions(+), 3 deletions(-) diff --git a/news/2024-06-12-4-2-0-Alpha1.md b/news/2024-06-12-4-2-0-Alpha1.md index ec313ee87f..f3efb24e42 100644 --- a/news/2024-06-12-4-2-0-Alpha1.md +++ b/news/2024-06-12-4-2-0-Alpha1.md @@ -24,15 +24,17 @@ In previous versions of netty the `EventLoopGroup` implementation was tightly co This has changed in 4.2.0, here you will use one `EventLoopGroup` implementation for all transports. This allows for easier customization of it (think of it like `ThreadPoolExecutor` that can be extended and customized). To make this possible we extracted the whole IO handling / multiplexing to another class that is injected into the `MultiThreadIoEventLoopGroup`. For example: -``` + +```java new EpollEventLoop(); ``` becomes -``` -new MultiThreadIoEventLoopGroup(EpollIoHandler.newFactory(); +```java +new MultiThreadIoEventLoopGroup(EpollIoHandler.newFactory(); ``` + Other transports follow the same pattern. `MultiThreadIoEventLoopGroup` and `SingleThreadIoEventLoop` provide various methods that can be overridden by the user and so provide the ability to: