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
Refactor the Peer struct by removing the cached SetupConnection in the struct, different devices may want to cache different messages relevant to them on sending their initial message for a connection e.g. Proxy might want to cache SetupConnection.Success where a PoolServer may want to cache SetupConnection.
Really the decision about what message should be cached should be made upstream (crate, project etc..) and the Peer really just becomes an outbound message buffer of Messages for a particular Channel/Connection
The text was updated successfully, but these errors were encountered:
Refactor the Peer struct by removing the cached
SetupConnection
in the struct, different devices may want to cache different messages relevant to them on sending their initial message for a connection e.g. Proxy might want to cacheSetupConnection.Success
where a PoolServer may want to cacheSetupConnection
.Really the decision about what message should be cached should be made upstream (crate, project etc..) and the Peer really just becomes an outbound message buffer of
Messages
for a particular Channel/ConnectionThe text was updated successfully, but these errors were encountered: