You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The IO module type includes a conn type which—if I understand it correctly—should be a type that includes information about the client's connection to the server. Right now, the async implementation simply sets this to unit, and in fact conn doesn't seem to be used by that implementation at all. But while the lwt (unix) implementation does use it, it also tacks on an additional Cohttp.Connection.t value with it as well.
The IO.conn type's meaning and usage should be consistently recognized and applied by all backends. Related to inhabitedtype/ocaml-webmachine#19.
The text was updated successfully, but these errors were encountered:
The
IO
module type includes aconn
type which—if I understand it correctly—should be a type that includes information about the client's connection to the server. Right now, the async implementation simply sets this tounit
, and in factconn
doesn't seem to be used by that implementation at all. But while the lwt (unix) implementation does use it, it also tacks on an additionalCohttp.Connection.t
value with it as well.The
IO.conn
type's meaning and usage should be consistently recognized and applied by all backends. Related to inhabitedtype/ocaml-webmachine#19.The text was updated successfully, but these errors were encountered: