xzg 最近的时间轴更新 xzg 最近的时间轴更新 | xzgV2EX 第 352076 号会员，加入于 2018-09-25 20:37:23 +08:00 |
| 2019 版"完全不工作" 1 问与答 xzg 2019-12-14 08:33:57 AM 最后回复来自 weiruanniubi | 20 |
| 淘宝这个冻结有点恶心 问与答 xzg 2018-10-07 05:03:55 AM 最后回复来自 Destiny97 | 3 |
xzg 最近回复了
2020-09-08 13:16:40 +08:00 回复了 beryl 创建的主题 程序员 准备走了，如何准备？ |
我寻思这那边也有微软嘛
WH 招人工智障不
2020-05-18 18:31:57 +08:00 回复了 imdong 创建的主题 分享发现 别怪直男癌的礼物了：不是直男审美，是淘宝总给直男推荐直男审美。 |
那就送她拯救者吧
2020-05-14 21:43:50 +08:00 回复了 cmai 创建的主题 程序员 关于 jmm 内存模型的问题 |
@cmai 不是很明白，因为 jvm 何时刷新根据 cpu 指令之间的交互、cpu 调度等多种情况，具体你可能要看 jvm 源码了
2020-05-14 21:09:22 +08:00 回复了 cmai 创建的主题 程序员 关于 jmm 内存模型的问题 |
你把 flag 定义 volatile 试下，我怀疑是子线程修改后没有及时刷新到主内存。
算了 这个排版贼鸡儿恶心
不存在你想的那个问题，设备上报的数据是通过 decoder 是 ChannelInbound 的 handler，你下发的数据 write 是通过 ChannelHandlerContext 写入 ChannelOutbound。下面是官方的图
I/O Request
via Channel or
ChannelHandlerContext
|
+---------------------------------------------------+---------------+
| ChannelPipeline | |
| \|/ |
| +---------------------+ +-----------+----------+ |
| | Inbound Handler N | | Outbound Handler 1 | |
| +----------+----------+ +-----------+----------+ |
| /|\ | |
| | \|/ |
| +----------+----------+ +-----------+----------+ |
| | Inbound Handler N-1 | | Outbound Handler 2 | |
| +----------+----------+ +-----------+----------+ |
| /|\ . |
| . . |
| ChannelHandlerContext.fireIN_EVT() ChannelHandlerContext.OUT_EVT()|
| [ method call] [method call] |
| . . |
| . \|/ |
| +----------+----------+ +-----------+----------+ |
| | Inbound Handler 2 | | Outbound Handler M-1 | |
| +----------+----------+ +-----------+----------+ |
| /|\ | |
| | \|/ |
| +----------+----------+ +-----------+----------+ |
| | Inbound Handler 1 | | Outbound Handler M | |
| +----------+----------+ +-----------+----------+ |
| /|\ | |
+---------------+-----------------------------------+---------------+
| \|/
+---------------+-----------------------------------+---------------+
| | | |
| [ Socket.read() ] [ Socket.write() ] |
| |
| Netty Internal I/O Threads (Transport Implementation) |
+-------------------------------------------------------------------+
I/O Request
via Channel or
ChannelHandlerContext
|
+---------------------------------------------------+---------------+
| ChannelPipeline | |
| \|/ |
| +---------------------+ +-----------+----------+ |
| | Inbound Handler N | | Outbound Handler 1 | |
| +----------+----------+ +-----------+----------+ |
| /|\ | |
| | \|/ |
| +----------+----------+ +-----------+----------+ |
| | Inbound Handler N-1 | | Outbound Handler 2 | |
| +----------+----------+ +-----------+----------+ |
| /|\ . |
| . . |
| ChannelHandlerContext.fireIN_EVT() ChannelHandlerContext.OUT_EVT()|
| [ method call] [method call] |
| . . |
| . \|/ |
| +----------+----------+ +-----------+----------+ |
| | Inbound Handler 2 | | Outbound Handler M-1 | |
| +----------+----------+ +-----------+----------+ |
| /|\ | |
| | \|/ |
| +----------+----------+ +-----------+----------+ |
| | Inbound Handler 1 | | Outbound Handler M | |
| +----------+----------+ +-----------+----------+ |
| /|\ | |
+---------------+-----------------------------------+---------------+
| \|/
+---------------+-----------------------------------+---------------+
| | | |
| [ Socket.read() ] [ Socket.write() ] |
| |
| Netty Internal I/O Threads (Transport Implementation) |
+-------------------------------------------------------------------+
2019-12-13 13:04:06 +08:00 回复了 xzg 创建的主题 问与答 2019 版"完全不工作" |
@beingbin 看来我不配做个普通人
Select Language