[WIP][ISSUE #4426] Optimize EventMesh Bridge with QUIC #4427
Conversation
Signed-off-by: Yixiang Zhao <seriouszyx@foxmail.com>
Signed-off-by: Yixiang Zhao <seriouszyx@foxmail.com>
qqeasonchen
changed the title
| @@ -271,6 +272,9 @@ private void registerHTTPRequestProcessor() throws Exception { | |||
| final LocalSubscribeEventProcessor localSubscribeEventProcessor = new LocalSubscribeEventProcessor(this); | |||
| this.getHandlerService().register(localSubscribeEventProcessor, clientManageExecutor); | |||
|
|
|||
| final QuicLocalSubscribeEventProcessor quicLocalSubscribeEventProcessor = new QuicLocalSubscribeEventProcessor(this); | |||
| this.getHandlerService().register(quicLocalSubscribeEventProcessor, clientManageExecutor); | |||
There was a problem hiding this comment.
Could this QUIC protocol be made configurable? If not configured, it will be enabled or disabled by default.
可不可以把 QUIC 协议的方式做成可配置的？不配置话的就默认开启或不开启。
| Channel channel = bs.group(group) | ||
| .channel(NioDatagramChannel.class) | ||
| .handler(codec) | ||
| .bind(new InetSocketAddress(9999)).sync().channel(); |
There was a problem hiding this comment.
Can the port of this protocol be made configurable?
|
It has been 60 days since the last activity on this pull request. I am reaching out here to gently remind you that the Apache EventMesh community values every pull request, and please feel free to get in touch with the reviewers at any time. They are available to assist you in advancing the progress of your pull request and offering the latest feedback. If you encounter any challenges during development, seeking support within the community is encouraged. We sincerely appreciate your contributions to Apache EventMesh. |
|
Any progress we can make here? |
Fixes #4426.