We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
protocol
session
Ideally we would want protocol to know nothing of session. But currently there are several back-references:
LocalError
RemoteError
EchoRoundError
ReceiveError
protocol/serialization
WireFormat
Edit: Fixed/invalidated:
FirstRound::new()
SessionId
SessionParameters::Digest
Protocol
Digest
The text was updated successfully, but these errors were encountered:
fjarri
No branches or pull requests
Ideally we would want
protocol
to know nothing ofsession
. But currently there are several back-references:LocalError
andRemoteError
are used on both levels. Should we have each layer have their own?EchoRoundError
is declared at the session level, but used at the protocol level as one of the variants ofReceiveError
protocol/serialization
needs to know ofWireFormat
Edit: Fixed/invalidated:
FirstRound::new()
needs to know aboutSessionId
(see alsoSessionId
improvements #9) -SessionId
improvements #9 is closed by TieSessionId
toSessionParameters::Digest
#41,Protocol
trait usesDigest
trait, which is defined at the session level — using RustCrypto traits directly nowThe text was updated successfully, but these errors were encountered: