glennosss commented on pull request #924:
URL: https://github.com/apache/james-project/pull/924#issuecomment-1074760329


   Please cherry-pick: 
https://github.com/glennosss/james-project/commit/19ca9349f5a26e114c7acc1121bdc208be27e622
   From branch: https://github.com/glennosss/james-project/tree/netty4-combo
   
   Several fixes and improvements to make starting and managing netty servers 
easier - specifically:
   1. Created 'EventLoopGroupManager' interface - see interface javadoc for 
more information - allows much better control over starting/sharing 
EventLoopGroups - 
https://github.com/glennosss/james-project/blob/netty4-combo/protocols/netty/src/main/java/org/apache/james/protocols/netty/EventLoopGroupManager.java
   2. Updated 'Encryption' to support old static methods, but added additional 
static methods which add Netty SslContext support - see 'Encryption' javadoc 
for more information - 
https://github.com/glennosss/james-project/blob/netty4-combo/protocols/api/src/main/java/org/apache/james/protocols/api/Encryption.java
   3. See 'ProtocolServer' javadoc - now supports async bind/unbind, control 
over how long unbind takes, and added unbindNow() to help with instantly 
stopping server for unit tests - 
https://github.com/glennosss/james-project/blob/netty4-combo/protocols/api/src/main/java/org/apache/james/protocols/api/ProtocolServer.java
   4. Updated 'NettyServer', 'AbstractAsyncServer' to support proper 
construction using Factory/Builder approach - making it much easier to method 
chain and build a server.
   5. Updated 'AbstractConfigurableAsyncServer' to support Factory/Builder 
approach - also 'bossThreads' and 'keepalive' parameters are now configurable.
   
   FYI Also includes a fix for TCP_NODELAY still wasn't being set properly 
(`configureBootstrap()` was being run after socket was bound).


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]



---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to