Trait tokio_io::AsyncRead [−] [src]

pub trait AsyncRead: Read {
    unsafe fn prepare_uninitialized_buffer(&self, buf: &mut [u8]) -> bool { ... }

    fn read_buf<B: BufMut>(&mut self, buf: &mut B) -> Poll<usize, Error>
    where
        Self: Sized,
    { ... }

    fn framed<T: Encoder + Decoder>(self, codec: T) -> Framed<Self, T>
    where
        Self: AsyncWrite + Sized,
    { ... }

    fn split(self) -> (ReadHalf<Self>, WriteHalf<Self>)
    where
        Self: AsyncWrite + Sized,
    { ... }
}

A trait for readable objects which operated in an asynchronous and futures-aware fashion.

This trait inherits from io::Read and indicates as a marker that an I/O object is nonblocking, meaning that it will return an error instead of blocking when bytes are unavailable, but the stream hasn't reached EOF. Specifically this means that the read function for types that implement this trait can have a few return values:

This trait importantly means that the read method only works in the context of a future's task. The object may panic if used outside of a task.

Provided Methods

Prepares an uninitialized buffer to be safe to pass to read. Returns true if the supplied buffer was zeroed out.

While it would be highly unusual, implementations of io::Read are able to read data from the buffer passed as an argument. Because of this, the buffer passed to io::Read must be initialized memory. In situations where large numbers of buffers are used, constantly having to zero out buffers can be expensive.

This function does any necessary work to prepare an uninitialized buffer to be safe to pass to read. If read guarantees to never attempt read data out of the supplied buffer, then prepare_uninitialized_buffer doesn't need to do any work.

If this function returns true, then the memory has been zeroed out. This allows implementations of AsyncRead which are composed of multiple sub implementations to efficiently implement prepare_uninitialized_buffer.

This function isn't actually unsafe to call but unsafe to implement. The implementor must ensure that either the whole buf has been zeroed or read_buf() overwrites the buffer without reading it and returns correct value.

This function is called from read_buf.

Pull some bytes from this source into the specified Buf, returning how many bytes were read.

The buf provided will have bytes read into it and the internal cursor will be advanced if any bytes were read. Note that this method typically will not reallocate the buffer provided.

Provides a Stream and Sink interface for reading and writing to this Io object, using Decode and Encode to read and write the raw data.

Raw I/O objects work with byte sequences, but higher-level code usually wants to batch these into meaningful chunks, called "frames". This method layers framing on top of an I/O object, by using the Codec traits to handle encoding and decoding of messages frames. Note that the incoming and outgoing frame types may be distinct.

This function returns a single object that is both Stream and Sink; grouping this into a single object is often useful for layering things like gzip or TLS, which require both read and write access to the underlying object.

If you want to work more directly with the streams and sink, consider calling split on the Framed returned by this method, which will break them into separate objects, allowing them to interact more easily.

Helper method for splitting this read/write object into two halves.

The two halves returned implement the Read and Write traits, respectively.

Implementors