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
{{ message }}
This repository has been archived by the owner on Sep 6, 2022. It is now read-only.
A transport implementation should be able to signal the capabilities it has by default. Some transports might already have some of the layers we currently add on top, such as QUIC already having build in multiplexing, and cjdns already having transport level encryption.
This can even be extended to help us move to supporting unreliable transports.
I think some of the general traits we want to have are (non-exhaustively):
HasEncryption
HasMultiplexing
IsReliable
The text was updated successfully, but these errors were encountered:
Now that all transports are expose all required features, this is less of an issue (no more HasEncryption, HasMultiplexing, IsReliable). However, we will likely still want "traits" for optional (but useful) features.
A transport implementation should be able to signal the capabilities it has by default. Some transports might already have some of the layers we currently add on top, such as QUIC already having build in multiplexing, and cjdns already having transport level encryption.
This can even be extended to help us move to supporting unreliable transports.
I think some of the general traits we want to have are (non-exhaustively):
The text was updated successfully, but these errors were encountered: