QuicOperations should extend ChannelOperations<UdpInbound, UdpOutbound>

[linux-china]

Now the QuicOperations is different with UdpOperations, HttpOperations, and not extends ChannelOperations<UdpInbound, UdpOutbound> .

To implement the QUIC transport for RSocket with following code:

return quicServer
                .doOnConnection(
                        c -> {
                            c.addHandlerLast(new RSocketLengthCodec(maxFrameLength));
                            acceptor.apply(new QuicDuplexConnection(c))
                                    .then(Mono.<Void>never())
                                    .subscribe(c.disposeSubscriber());
                        })
                .bind()
                .map(CloseableChannel::new);

receive() in QuicDuplexConnection as following:

    public Flux<ByteBuf> receive() {
        return connection.inbound().receive().map(FrameLengthCodec::frame);
    }

QuicOperations.inbound() can not receive any ByteBuf because it use reactor.netty.Connection default method as following:

      default NettyInbound inbound() {
		return ReactorNetty.unavailableInbound(this);
	}

[violetagg]

@linux-china Do you need to add this on connection level or stream level?
If you need to add this on stream level see this test https://github.com/reactor/reactor-netty/blob/main/reactor-netty-incubator-quic/src/test/java/reactor/netty/incubator/quic/QuicClientSmokeTests.java

[linux-china]

@violetagg Got, and I will take a look. rsocket-transport-quic is here https://github.com/linux-china/rsocket-transport-quic/blob/master/src/main/java/io/rsocket/transport/quic/server/QuicServerTransport.java Still not lucky to make it work on server side. Maybe I did some stupid things :).

client side:

server side:

[violetagg]

@linux-china Let's continue the discussion about integration in RSocket here rsocket/rsocket-java#1019
If something is needed on Reactor Netty side we can address it.