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

Unify API #24

Open
sehz opened this issue Jun 3, 2020 · 1 comment
Open

Unify API #24

sehz opened this issue Jun 3, 2020 · 1 comment

Comments

@sehz
Copy link

sehz commented Jun 3, 2020

In the async-native-tls, there is a single TlsStream, but in this crate, there are two different Stream implementation. It would be nice if we have unified API that can support different engine.

@skade
Copy link
Collaborator

skade commented Jun 4, 2020

I'm trying to remember what the exact cause for having both streams was. I tried unifying both of them a while back, but if I remember right, it's at least not trivial, at least without dynamic dispatch.

That said, I'd prefer one TLS implementation for all runtimes.

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

2 participants