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

Proposal: A shared trait for tls acceptors that are implemented by both async-tls and async-native-tls #43

Open
jbr opened this issue Feb 4, 2021 · 0 comments

Comments

@jbr
Copy link
Contributor

jbr commented Feb 4, 2021

I have some code that implements this using wrapper types, but would really love for a trait like this to exist:

A proposed async-tls-acceptor crate that publishes this trait:

#[async_trait]
pub trait Acceptor<Input>: Clone + Send + Sync + 'static
where
    Input: AsyncRead + AsyncWrite + Send + Sync + Unpin + 'static,
{
    type Output: AsyncRead + AsyncWrite + Send + Sync + Unpin + 'static;
    type Error: std::fmt::Debug + Send + Sync;

    async fn accept(&self, input: Input) -> Result<Self::Output, Self::Error>;
}

The implementation for async-tls would be:

#[async_trait]
impl<Input> Acceptor<Input> for async_tls::TlsAcceptor
where
    Input: AsyncRead + AsyncWrite + Send + Sync + Unpin + 'static,
{
    type Output = async_tls::TlsStream<Input>;
    type Error = std::io::Error;
    async fn accept(&self, input: Input) -> Result<Self::Output, Self::Error> {
        async_tls::TlsAcceptor::accept(&self, input).await
    }
}

Would this be welcomed?

refs: async-email/async-native-tls#27

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