NOTE
Netty Source: Registering Read Interest
How an active socket channel becomes interested in read readiness and feeds inbound pipeline events.
This is a historical learning note and may contain outdated or incomplete understanding.
Once an accepted channel is registered/active and configured to read, its transport registers or updates read interest with the selector. When readiness arrives, the event loop reads bytes/messages according to the channel’s receive allocator/policy and fires inbound events through the pipeline.
One readiness notification can yield zero, one, or multiple read operations/messages depending on transport/buffer/framing behavior.
Do not equate selector read readiness with one complete application request.