Supports pipelining requests and reusing open connections.
ep.GetHttpConnection(c => {
connection.OnRequest(head, body, responseDelegate);
});
This makes me think:
When writes are made during a single iteration of the runloop, the socket implementation should combine them into a single packet. In other words, writes are deferred until the end of the loop and always re-buffered or use scatter/gather APIs.
This is so that user can control pipelining of requests. Very nice also in the outgoing message queue because headers and synchronous bodies are condensed into a single packet.
Supports pipelining requests and reusing open connections.
This makes me think:
When writes are made during a single iteration of the runloop, the socket implementation should combine them into a single packet. In other words, writes are deferred until the end of the loop and always re-buffered or use scatter/gather APIs.
This is so that user can control pipelining of requests. Very nice also in the outgoing message queue because headers and synchronous bodies are condensed into a single packet.