Netty Concepts: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
|||
| Line 14: | Line 14: | ||
Netty is both a framework and a class library. | Netty is both a framework and a class library. | ||
The ChannelHandlerContext represents the binding between the ChannelPipeline and its installed handlers. | |||
Revision as of 22:03, 15 September 2020
Internal
Overview
High throughput non-blocking I/O. Servers and clients. Channel. ChannelPipeline that holds ChannelHandler instances. ChannelHandler is important because it represents the interface between networking concerns and application business logic. Events. Everything is an event (accept new connection, read data, write data - in this context data is an event). Event lifecycle. Events are processed by EventLoops.
Transport and NIO Transport.
Both the server and the client go through a bootstrapping process. This is where the business logic (ChannelHandlers) is "deployed".
Netty is both a framework and a class library.
The ChannelHandlerContext represents the binding between the ChannelPipeline and its installed handlers.