You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have confirmed that this should be classified as an enhancement rather than a bug/feature.
Summary
Introduce a new event NettyEventType.ACTIVE, implement channelActive for NettyRemotingClient#NettyConnectManageHandler
and add onChannelActive for ChannelEventListener.
Motivation
The ChannelEventListener in NettyRemotingClient lacks a response to channelActive. In contrast, the ChannelEventListener in NettyRemotingServer handles channelActive, but generates NettyEventType.CONNECT events.
Since the ChannelEventListener in NettyRemotingClient already handles channelConnect using NettyEventType.CONNECT, we should introduce a new event, NettyEventType.ACTIVE, to handle channelActive in NettyRemotingClient.
This plan focuses solely on the ACTIVE event for NettyRemotingClient and does not address the semantics of CONNECT and ACTIVE in NettyRemotingServer, which will be considered for correction in the future.
Describe the Solution You'd Like
Add the ACTIVE event only for NettyRemotingClient.
Describe Alternatives You've Considered
Address the semantics of CONNECT and ACTIVE in NettyRemotingServer.
Additional Context
No response
The text was updated successfully, but these errors were encountered:
drpmma
changed the title
[Enhancement] Add channelActive for NettyRemotingClient#NettyConnectManageHandler
[Enhancement] Introduce a new event NettyEventType.ACTIVE for ChannelEventListener
Oct 23, 2023
drpmma
added a commit
to drpmma/rocketmq
that referenced
this issue
Oct 23, 2023
…hannelEventListener
* introduce a new event NettyEventType.ACTIVE,
* implement channelActive interface for NettyRemotingClient#NettyConnectManageHandler
* add onChannelActive for ChannelEventListener interface.
* [ISSUE #7493] Introduce a new event NettyEventType.ACTIVE for ChannelEventListener
* introduce a new event NettyEventType.ACTIVE,
* implement channelActive interface for NettyRemotingClient#NettyConnectManageHandler
* add onChannelActive for ChannelEventListener interface.
* Move send heartbeat to onChannelActive
Before Creating the Enhancement Request
Summary
Introduce a new event
NettyEventType.ACTIVE
, implementchannelActive
forNettyRemotingClient#NettyConnectManageHandler
and add
onChannelActive
forChannelEventListener
.Motivation
The
ChannelEventListener
inNettyRemotingClient
lacks a response tochannelActive
. In contrast, theChannelEventListener
inNettyRemotingServer
handleschannelActive
, but generatesNettyEventType.CONNECT
events.Since the
ChannelEventListener
inNettyRemotingClient
already handleschannelConnect
usingNettyEventType.CONNECT
, we should introduce a new event,NettyEventType.ACTIVE
, to handlechannelActive
inNettyRemotingClient
.This plan focuses solely on the
ACTIVE
event forNettyRemotingClient
and does not address the semantics ofCONNECT
andACTIVE
inNettyRemotingServer
, which will be considered for correction in the future.Describe the Solution You'd Like
Add the
ACTIVE
event only forNettyRemotingClient
.Describe Alternatives You've Considered
Address the semantics of
CONNECT
andACTIVE
inNettyRemotingServer
.Additional Context
No response
The text was updated successfully, but these errors were encountered: