@UnstableApi public final class Http2MultiplexHandler extends Http2ChannelDuplexHandler
Http2FrameCodec.
When a new stream is created, a new Http2StreamChannel is created for it. Applications send and
receive Http2StreamFrames on the created channel. ByteBufs cannot be processed by the channel;
all writes that reach the head of the pipeline must be an instance of Http2StreamFrame. Writes that reach
the head of the pipeline are processed directly by this handler and cannot be intercepted.
The child channel will be notified of user events that impact the stream, such as Http2GoAwayFrame and Http2ResetFrame, as soon as they occur. Although Http2GoAwayFrame and Http2ResetFrame signify that the remote is ignoring further
communication, closing of the channel is delayed until any inbound queue is drained with Channel.read(), which follows the default behavior of channels in Netty. Applications are
free to close the channel in response to such events if they don't have use for any queued
messages. Any connection level events like Http2SettingsFrame and Http2GoAwayFrame
will be processed internally and also propagated down the pipeline for other handlers to act on.
Outbound streams are supported via the Http2StreamChannelBootstrap.
ChannelConfig.setMaxMessagesPerRead(int) and ChannelConfig.setAutoRead(boolean) are supported.
Http2StreamFrames implement the ReferenceCounted interface, as they carry
reference counted objects (e.g. ByteBufs). The multiplex codec will call ReferenceCounted.retain()
before propagating a reference counted object through the pipeline, and thus an application handler needs to release
such an object after having consumed it. For more information on reference counting take a look at
the reference counted docs.
EventLoop. Therefore, an active channel
does not map to an active HTTP/2 stream immediately. Only once a Http2HeadersFrame has been successfully sent
or received, does the channel map to an active HTTP/2 stream. In case it is not possible to open a new HTTP/2 stream
(i.e. due to the maximum number of active streams being exceeded), the child channel receives an exception
indicating the cause and is closed immediately thereafter.
ChannelHandlers are free to ignore the channel's writability, in which case the excessive writes will
be buffered by the parent channel. It's important to note that only Http2DataFrames are subject to
HTTP/2 flow control.
Http2StreamChannelHttp2StreamChannel a Http2ResetFrame will be sent to the remote peer with
Http2Error.CANCEL if needed. If you want to close the stream with another Http2Error (due
errors / limits) you should propagate a Http2FrameStreamException through the ChannelPipeline.
Once it reaches the end of the ChannelPipeline it will automatically close the Http2StreamChannel
and send a Http2ResetFrame with the unwrapped Http2Error set. Another possibility is to just
directly write a Http2ResetFrame to the Http2StreamChannell.ChannelHandler.Sharable| 构造器和说明 |
|---|
Http2MultiplexHandler(ChannelHandler inboundStreamHandler)
Creates a new instance
|
Http2MultiplexHandler(ChannelHandler inboundStreamHandler,
ChannelHandler upgradeStreamHandler)
Creates a new instance
|
forEachActiveStream, handlerAdded, handlerRemoved, newStreambind, close, connect, deregister, disconnect, flush, read, writechannelActive, channelInactive, channelRegistered, channelUnregisteredensureNotSharable, isSharablepublic Http2MultiplexHandler(ChannelHandler inboundStreamHandler)
inboundStreamHandler - the ChannelHandler that will be added to the ChannelPipeline of
the Channels created for new inbound streams.public Http2MultiplexHandler(ChannelHandler inboundStreamHandler, ChannelHandler upgradeStreamHandler)
inboundStreamHandler - the ChannelHandler that will be added to the ChannelPipeline of
the Channels created for new inbound streams.upgradeStreamHandler - the ChannelHandler that will be added to the ChannelPipeline of the
upgraded Channel.protected void handlerAdded0(ChannelHandlerContext ctx)
protected void handlerRemoved0(ChannelHandlerContext ctx)
public void channelRead(ChannelHandlerContext ctx, java.lang.Object msg) throws java.lang.Exception
ChannelInboundHandlerAdapterChannelHandlerContext.fireChannelRead(Object) to forward
to the next ChannelInboundHandler in the ChannelPipeline.
Sub-classes may override this method to change behavior.channelRead 在接口中 ChannelInboundHandlerchannelRead 在类中 ChannelInboundHandlerAdapterjava.lang.Exceptionpublic void channelWritabilityChanged(ChannelHandlerContext ctx) throws java.lang.Exception
ChannelInboundHandlerAdapterChannelHandlerContext.fireChannelWritabilityChanged() to forward
to the next ChannelInboundHandler in the ChannelPipeline.
Sub-classes may override this method to change behavior.channelWritabilityChanged 在接口中 ChannelInboundHandlerchannelWritabilityChanged 在类中 ChannelInboundHandlerAdapterjava.lang.Exceptionpublic void userEventTriggered(ChannelHandlerContext ctx, java.lang.Object evt) throws java.lang.Exception
ChannelInboundHandlerAdapterChannelHandlerContext.fireUserEventTriggered(Object) to forward
to the next ChannelInboundHandler in the ChannelPipeline.
Sub-classes may override this method to change behavior.userEventTriggered 在接口中 ChannelInboundHandleruserEventTriggered 在类中 ChannelInboundHandlerAdapterjava.lang.Exceptionpublic void exceptionCaught(ChannelHandlerContext ctx, java.lang.Throwable cause) throws java.lang.Exception
ChannelInboundHandlerAdapterChannelHandlerContext.fireExceptionCaught(Throwable) to forward
to the next ChannelHandler in the ChannelPipeline.
Sub-classes may override this method to change behavior.exceptionCaught 在接口中 ChannelHandlerexceptionCaught 在接口中 ChannelInboundHandlerexceptionCaught 在类中 ChannelInboundHandlerAdapterjava.lang.Exceptionpublic void channelReadComplete(ChannelHandlerContext ctx) throws java.lang.Exception
channelReadComplete 在接口中 ChannelInboundHandlerchannelReadComplete 在类中 ChannelInboundHandlerAdapterjava.lang.Exception