As per #1120, our work to add support for proxying client requests in cohttp-eio is following the precedent set by the work for cohttp-lwt in #1080
In cohttp-lwt the client request proxying is supplied via its connection cache mechanism. Among other benefits, this makes it so that users of other libraries implemented with cohttp-lwt can set run requests thru proxies by changing the cache (via a stateful updates to the environment), instead of having to extend or rewrite the libraries.
This general design decision entails to an obvious prerequisite: we must first implement basic support for caching connections in the cohttp-eio.
As per #1120, our work to add support for proxying client requests in cohttp-eio is following the precedent set by the work for cohttp-lwt in #1080
In cohttp-lwt the client request proxying is supplied via its connection cache mechanism. Among other benefits, this makes it so that users of other libraries implemented with cohttp-lwt can set run requests thru proxies by changing the cache (via a stateful updates to the environment), instead of having to extend or rewrite the libraries.
This general design decision entails to an obvious prerequisite: we must first implement basic support for caching connections in the cohttp-eio.