[aryan-25]

Motivation

We currently allocate for a class in both the request reader and response writer. This class tracks whether the reader/writer have finished reading the request / writing the response. Both of these properties are read by the same caller. We can therefore save an allocation if we share this state across both the reader and writer.

Modifications

• Introduced an ExchangeState type which replaces the state classes of the reader and response writer.
• Introduced an ancillary type HTTP1ConnectionReuseCoordinator to encapsulate the iterator moving logic required for connection re-use.

Result

An allocation saved for each request.

[FranzBusch]

I think this looks okay for now. In the future we can completely get rid of this allocation by making the reader and writer ~Escapable and using a MutableRef to share the state into the reader/writer and read it out after the response handler is done