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

Transport interface lacking #52

Open
ghost opened this issue Aug 24, 2020 · 0 comments
Open

Transport interface lacking #52

ghost opened this issue Aug 24, 2020 · 0 comments

Comments

@ghost
Copy link

ghost commented Aug 24, 2020

The current Transport interface does not seem suitable for transports that are not request-response oriented.

With HTTP, the correlation of request to response is part of the protocol. I have a project where I'm using a raw socket. Once I get a message, I need to still inspect it to see if the id of a response matches a previously sent request. So I end up having to decode to JSON anyway and so JSON decoding happens twice in the app.

I'm not sure of the best way forward.

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

0 participants