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 am using Netty Quic Codec for messaging in a P2P network.
My approach at present works on the first message but fails to connect on the second message.
Comments on the following assumptions would be appreciated.
The client is created once and remains open until the system closes down. (Transport Layer)
A QuicChannel once created remains available until closed. (Child of the Client)
Many QuicChannels as children of the client can be created to different network addresses.
A QuicChannel can create many streamChannels which can be opened and when necessary closed using FIN (fin frame).
Questions..
Will a connection fail if a QuicChannel is created to an address that already has a QuicChannel setup?
Is Netty Quic Codec at it's current state of development usable for P2P messaging?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
I am using Netty Quic Codec for messaging in a P2P network.
My approach at present works on the first message but fails to connect on the second message.
Comments on the following assumptions would be appreciated.
Questions..
Beta Was this translation helpful? Give feedback.
All reactions