Netty源码分析之ChannelEvent

ChannelEvent是和这个Channel相关的IO事件和请求,会由各个ChannelHandler来处理。
事件分为上行(Upstream)和下行(Downstream)两种。
当服务器从客户端收到一个消息,那么与之相关的就是一个上行事件(Upstream Event),流水线(Pipeline)中的UpstreamChannelHandler会处理它;如果服务器要响应这个客户端,那么与响应消息对应的就是下行事件(Downstream Event),流水线(Pipeline)中的DownstreamChannelHandler会处理它。

org.jboss.netty.channel.ChannelEvent源码:

public interface ChannelEvent {

    /**
     * Returns the {@link Channel} which is associated with this event.
     */
    Channel getChannel();

    /**
     * Returns the {@link ChannelFuture} which is associated with this event.
     * If this event is an upstream event, this method will always return a
     * {@link SucceededChannelFuture} because the event has occurred already.
     * If this event is a downstream event (i.e. I/O request), the returned
     * future will be notified when the I/O request succeeds or fails.
     */
    ChannelFuture getFuture();
}

An I/O event or I/O request associated with a Channel.

A ChannelEvent is handled by a series of ChannelHandlers in a ChannelPipeline.

Upstream events and downstream events, and their interpretation
Every event is either an upstream event or a downstream event. If an event flows forward from the first handler to the last handler in a ChannelPipeline, we call it an upstream event and say "an event goes upstream." If an event flows backward from the last handler to the first handler in a ChannelPipeline, we call it a downstream event and say "an event goes downstream." (Please refer to the diagram in ChannelPipeline for more explanation.)

When your server receives a message from a client, the event associated with the received message is an upstream event. When your server sends a message or reply to the client, the event associated with the write request is a downstream event. The same rule applies for the client side. If your client sent a request to the server, it means your client triggered a downstream event. If your client received a response from the server, it means your client will be notified with an upstream event. Upstream events are often the result of inbound operations such as InputStream.read(byte[]), and downstream events are the request for outbound operations such as OutputStream.write(byte[]), Socket.connect(SocketAddress), and Socket.close().

Upstream events

Event name Event type and condition Meaning
"messageReceived" MessageEvent a message object (e.g. ChannelBuffer) was received from a remote peer
"exceptionCaught" ExceptionEvent an exception was raised by an I/O thread or a ChannelHandler
"channelOpen" ChannelStateEvent(state = OPEN, value = true) a Channel is open, but not bound nor connected
"channelClosed" ChannelStateEvent(state = OPEN, value = false) a Channel was closed and all its related resources were released
"channelBound" ChannelStateEvent(state = BOUND, value = SocketAddress) a Channel is open and bound to a local address, but not connected
"channelUnbound" ChannelStateEvent(state = BOUND, value = null) a Channel was unbound from the current local address
"channelConnected" ChannelStateEvent(state = CONNECTED, value = SocketAddress) a Channel is open, bound to a local address, and connected to a remote address
"writeComplete" WriteCompletionEvent something has been written to a remote peer
"channelDisconnected" ChannelStateEvent(state = CONNECTED, value = null) a Channel was disconnected from its remote peer
"channelInterestChanged" ChannelStateEvent(state = INTEREST_OPS, no value) a Channel's interestOps was changed

These two additional event types are used only for a parent channel which can have a child channel (e.g. ServerSocketChannel).

Event name Event type and condition Meaning
"childChannelOpen" ChildChannelStateEvent(childChannel.isOpen() = true) a child Channel was open (e.g. a server channel accepted a connection.)
"childChannelClosed" ChildChannelStateEvent(childChannel.isOpen() = false) a child Channel was closed (e.g. the accepted connection was closed.)

Downstream events

Event name Event type and condition Meaning
"write" MessageEvent Send a message to the Channel.
"bind" ChannelStateEvent(state = BOUND, value = SocketAddress) Bind the Channel to the specified local address.
"unbind" ChannelStateEvent(state = BOUND, value = null) Unbind the Channel from the current local address.
"connect" ChannelStateEvent(state = CONNECTED, value = SocketAddress) Connect the Channel to the specified remote address.
"disconnect" ChannelStateEvent(state = CONNECTED, value = null) Disconnect the Channel from the current remote address.
"close" ChannelStateEvent(state = OPEN, value = false) Close the Channel.
最后编辑于
©著作权归作者所有,转载或内容合作请联系作者
  • 序言:七十年代末,一起剥皮案震惊了整个滨河市,随后出现的几起案子,更是在滨河造成了极大的恐慌,老刑警刘岩,带你破解...
    沈念sama阅读 202,332评论 5 475
  • 序言:滨河连续发生了三起死亡事件,死亡现场离奇诡异,居然都是意外死亡,警方通过查阅死者的电脑和手机,发现死者居然都...
    沈念sama阅读 84,930评论 2 379
  • 文/潘晓璐 我一进店门,熙熙楼的掌柜王于贵愁眉苦脸地迎上来,“玉大人,你说我怎么就摊上这事。” “怎么了?”我有些...
    开封第一讲书人阅读 149,204评论 0 335
  • 文/不坏的土叔 我叫张陵,是天一观的道长。 经常有香客问我,道长,这世上最难降的妖魔是什么? 我笑而不...
    开封第一讲书人阅读 54,348评论 1 272
  • 正文 为了忘掉前任,我火速办了婚礼,结果婚礼上,老公的妹妹穿的比我还像新娘。我一直安慰自己,他们只是感情好,可当我...
    茶点故事阅读 63,356评论 5 363
  • 文/花漫 我一把揭开白布。 她就那样静静地躺着,像睡着了一般。 火红的嫁衣衬着肌肤如雪。 梳的纹丝不乱的头发上,一...
    开封第一讲书人阅读 48,447评论 1 281
  • 那天,我揣着相机与录音,去河边找鬼。 笑死,一个胖子当着我的面吹牛,可吹牛的内容都是我干的。 我是一名探鬼主播,决...
    沈念sama阅读 37,862评论 3 394
  • 文/苍兰香墨 我猛地睁开眼,长吁一口气:“原来是场噩梦啊……” “哼!你这毒妇竟也来了?” 一声冷哼从身侧响起,我...
    开封第一讲书人阅读 36,516评论 0 256
  • 序言:老挝万荣一对情侣失踪,失踪者是张志新(化名)和其女友刘颖,没想到半个月后,有当地人在树林里发现了一具尸体,经...
    沈念sama阅读 40,710评论 1 295
  • 正文 独居荒郊野岭守林人离奇死亡,尸身上长有42处带血的脓包…… 初始之章·张勋 以下内容为张勋视角 年9月15日...
    茶点故事阅读 35,518评论 2 318
  • 正文 我和宋清朗相恋三年,在试婚纱的时候发现自己被绿了。 大学时的朋友给我发了我未婚夫和他白月光在一起吃饭的照片。...
    茶点故事阅读 37,582评论 1 329
  • 序言:一个原本活蹦乱跳的男人离奇死亡,死状恐怖,灵堂内的尸体忽然破棺而出,到底是诈尸还是另有隐情,我是刑警宁泽,带...
    沈念sama阅读 33,295评论 4 318
  • 正文 年R本政府宣布,位于F岛的核电站,受9级特大地震影响,放射性物质发生泄漏。R本人自食恶果不足惜,却给世界环境...
    茶点故事阅读 38,848评论 3 306
  • 文/蒙蒙 一、第九天 我趴在偏房一处隐蔽的房顶上张望。 院中可真热闹,春花似锦、人声如沸。这庄子的主人今日做“春日...
    开封第一讲书人阅读 29,881评论 0 19
  • 文/苍兰香墨 我抬头看了看天上的太阳。三九已至,却和暖如春,着一层夹袄步出监牢的瞬间,已是汗流浃背。 一阵脚步声响...
    开封第一讲书人阅读 31,121评论 1 259
  • 我被黑心中介骗来泰国打工, 没想到刚下飞机就差点儿被人妖公主榨干…… 1. 我叫王不留,地道东北人。 一个月前我还...
    沈念sama阅读 42,737评论 2 349
  • 正文 我出身青楼,却偏偏与公主长得像,于是被迫代替她去往敌国和亲。 传闻我的和亲对象是个残疾皇子,可洞房花烛夜当晚...
    茶点故事阅读 42,280评论 2 341

推荐阅读更多精彩内容