Struct PersistentHttpConnection 

pub struct PersistentHttpConnection { /* private fields */ }

Encapsulates a HttpClientSession, enabling multiple requests to be queued and used on a single session.

It ensures only one request can be in flight at a time, and will buffer the request until the connection is established. This utilizes HTTP 1.x keep-alive headers to attempt to re-use the same connection for multiple requests.

Requests are started by calling PersistentHttpConnection::request, which will return a PendingHttpResponse. These pending http response will coordinate with one another to send requests and drive responses in the order the function was called.

An HTTP server may elect to close an http session at any time. When this occurs, a new PersistentHttpConnection must be created from the original HttpClient.

Implementations

impl PersistentHttpConnection

pub fn request<I: IntoBody>( &mut self, request: Request<I>, ) -> Result<PendingHttpResponse, Error>

Trait Implementations

impl Debug for PersistentHttpConnection

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

Formats the value using the given formatter.

impl From<HttpClientSession> for PersistentHttpConnection

fn from(session: HttpClientSession) -> Self

Converts to this type from the input type.

impl Session for PersistentHttpConnection

fn status(&self) -> SessionStatus

Check the current session status.

fn drive(&mut self) -> Result<DriveOutcome, Error>

Some implementations will internally buffer payloads or require a duty cycle to drive callbacks. Those implementations will require drive(..) to be called continuously to completely publish and/or receive data. This function will return DriveOutcome::Active if work was done, indicating to any scheduler that more work may be pending. When this function returns DriveOutcome::Idle, only then should it indicate to a scheduler that yielding or idling is appropriate.