mirage-conduit

MirageOS interface to network connections
README

The conduit library takes care of establishing and listening for
TCP and SSL/TLS connections for the Lwt and Async libraries.

The reason this library exists is to provide a degree of abstraction
from the precise SSL library used, since there are a variety of ways
to bind to a library (e.g. the C FFI, or the Ctypes library), as well
as well as which library is used (just OpenSSL for now).

By default, OpenSSL is used as the preferred connection library, but
you can force the use of the pure OCaml TLS stack by setting the
environment variable CONDUIT_TLS=native when starting your program.

The opam packages available are:

  • conduit: the main Conduit module

  • conduit-lwt: the portable Lwt implementation

  • conduit-lwt-unix: the Lwt/Unix implementation

  • conduit-async the Jane Street Async implementation

  • mirage-conduit: the MirageOS compatible implementation

Debugging

Some of the Lwt_unix-based modules use a non-empty CONDUIT_DEBUG
environment variable to output debugging information to standard error.
Just set this variable when running the program to see what URIs
are being resolved to.

Further Informartion

Install
Published
16 Jul 2019
Maintainers
Sources
conduit-v1.5.0.tbz
sha256=06b6476ba4d8caf4cbfccbf7fd181cb2e5fe459e5e8e4992617fd2d7bebcbfd1
sha512=8bddae1a238d58d1b59520afb4f627c4beaf9b5355cacc4087e6667e678392cbc681777e32874ee033ffe40da8a7f0d3bab38eed64f25d201294a9c3e3476978
Dependencies
ipaddr
>= "3.0.0"
tls
>= "0.8.0" & < "0.11.0"
vchan
>= "3.0.0"
conduit-lwt
>= "1.5.0"
mirage-dns
>= "3.0.0" & < "4.0.0"
cstruct
>= "3.0.0"
ppx_sexp_conv
>= "v0.9.0"
ocaml
>= "4.03.0"
Reverse Dependencies
cohttp-mirage
< "2.3.0"
git-mirage
>= "1.11.2" & < "2.1.1"
h2-mirage
< "0.4.0"
mirage-http
>= "2.3.0"
resp-mirage
< "0.10.0"