Struct in_stream::InStreamTls

pub struct InStreamTls<Sub: InStreamStd> { /* fields omitted */ }

basic tls wrapper stream

Implementations

impl<Sub: InStreamStd> InStreamTls<Sub>

pub fn connect(url: &Url2, config: TlsConnectConfig) -> Result<Self>

Trait Implementations

impl<Sub: InStreamStd> Debug for InStreamTls<Sub>

fn fmt(&self, f: &mut Formatter<'_>) -> Result

Formats the value using the given formatter.

impl<Sub: InStreamStd, '_, '_> InStream<&'_ mut [u8], &'_ [u8]> for InStreamTls<Sub>

const URL_SCHEME: &'static str

your implementation should work with a single url scheme/protocol if you need to support multiple (i.e. ws:// vs wss://) consider using macros/code generation to DRY

fn raw_connect<C: InStreamConfig>(url: &Url2, config: C) -> Result<Self>

create a new connection / stream of this type. this function does the actual work of connecting, but it is recommended your struct provide a wrapper with a concrete config type

fn check_ready(&mut self) -> Result<bool>

process the stream to see if any remaining handshake items can be completed returns true if stream is set-up and ready to send/receive note that you can write before this function returns true but your messages may be buffered / sent later

fn remote_url(&self) -> Url2

access the remote url this connection represents

fn read(&mut self, data: &mut [u8]) -> Result<usize>

non-blocking read. if R is an array-type, success result is number of elements read otherwise it is 1

fn write(&mut self, data: &[u8]) -> Result<usize>

buffered write. Implementors should buffer data on WouldBlock

fn flush(&mut self) -> Result<()>

blocking flush all pending buffered write data.

impl<Sub: InStreamStd> InStreamStd for InStreamTls<Sub>

fn into_std_stream(self) -> StdStreamAdapter<Self>