-
Notifications
You must be signed in to change notification settings - Fork 354
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
QUIC Transport Support #1019
Comments
Hey @atshow! In short - we do plan! Stay tuned! |
I have raised the issue reactor/reactor-netty#1463 |
@OlegDokuka do you have any demo for RSocket on QUIC? https://github.com/reactor/reactor-netty/releases/tag/v1.0.12 |
@linux-china not at the moment. That requires ground rework of the transport API that we have right now. I have touched the ground in rsocket-js rework, but this has to be ported to java impl. Also, I presented the basic architecture in this slides -> https://www.icloud.com/keynote/0XbQI-VRGW0CPBBRVE_79BvOA#RSocket_over_QUIC |
@OlegDokuka @violetagg How about a demo transport implementation for QUIC ? and |
@linux-china I was planning to release QUIC support in 1.2.x once the transport API is reworked to offer proper abstraction for transports that have a built-in multiplexer/demultiplexer (e. g. QUIC or HTTP/2 or HTTP/3). However, we can always offer experimental preview support earlier. |
@OlegDokuka Any news on this topic? Anything the community can help with? Maybe with testing previews? |
@mepeisen there is a branch - https://github.com/rsocket/rsocket-java/tree/enhancement/aeron-support, the main problem is memory leak which I fail to track and there is a lack of time on my end to finish that effort |
@OlegDokuka is there a bit of code (test, example) that triggers the memory leak ? |
We know QUIC has become the IETF standard, and netty supports QUIC . Do we have any plans to support it?
The text was updated successfully, but these errors were encountered: