Skip to content

Decouple protocol and session levels #25

@fjarri

Description

@fjarri

Ideally we would want protocol to know nothing of session. But currently there are several back-references:

  • LocalError and RemoteError 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 of ReceiveError
  • protocol/serialization needs to know of WireFormat

Edit: Fixed/invalidated:

Metadata

Metadata

Assignees

Labels

APIInvolves backwards-incompatible changes of the public APIcode qualityMaking things simpler

Type

No type

Projects

No projects

Relationships

None yet

Development

No branches or pull requests

Issue actions