Skip to content
New issue

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

Server-side encoding/decoding #22

Open
sgg opened this issue Jun 19, 2020 · 0 comments
Open

Server-side encoding/decoding #22

sgg opened this issue Jun 19, 2020 · 0 comments
Assignees

Comments

@sgg
Copy link
Owner

sgg commented Jun 19, 2020

The client half of the types provided by Brokaw more or less boils down to two things:

  1. Command encoding (implemented via ToString Encode)
  2. Response decoding (implemented via TryFrom<RawResponse>)

One could extend Brokaw to support server-side connections by implementing (1) command decoding and (2) response encoding.

It might be worthwhile to reconsider the use of ToString as a trait for command encoding as it prevents Brokaw from supporting non UTF-8 messages (tracked in #26)

@sgg sgg self-assigned this Oct 17, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant