Netty Concepts: Difference between revisions
Jump to navigation
Jump to search
| Line 7: | Line 7: | ||
=Overview= | =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). Event lifecycle. Events are processed by EventLoops. | 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. | Transport and NIO Transport. | ||
Revision as of 21:53, 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.
Netty is both a framework and a class library.