NOTE
Netty Bind Source: Instantiating the Channel
Historical source flow from configured channel factory to a server Channel instance before registration.
This is a historical learning note and may contain outdated or incomplete understanding.
When bind/connect begins, Netty uses the configured channel factory/type to create a Channel implementation. The concrete channel wraps or coordinates the underlying Java/native transport object and creates channel-specific configuration/pipeline state.
Instantiation is only one phase; the channel must then be initialized and registered with an event loop before normal asynchronous operations proceed.
Concrete constructors and transport classes differ by Netty version/transport (NIO, epoll, kqueue, etc.).