conduit

AuthorsAnil Madhavapeddy, Thomas Leonard, Thomas Gazagnaire and Rudi Grinberg
LicenseISC
Homepagehttps://github.com/mirage/ocaml-conduit
Issue Trackerhttps://github.com/mirage/ocaml-conduit/issues
Tagorg:mirage
Maintaineranil@recoil.org
Dependencies
&cstruct>= 1.0.1
ipaddr>= 2.5.0&2.8.0
logs>= 0.5.0
ocamlbuild
ocamlfind
ppx_driverv0.10.0
ppx_optcomp>= 113.24.00
ppx_sexp_conv
sexplib
stringext
uri
Optional dependencies
|async
async_ssl
launchd
lwt
mirage-dns
mirage-types-lwt
ssl
tls
vchan
Availableocaml-version >= "4.02.3"
PublishedJan 4, 2017
Source [http] https://github.com/mirage/ocaml-conduit/archive/v0.14.4.tar.gz
671bc66a25c05ff37d36fcb731b9c8eb
StatisticsInstalled 16 times last month.
Edithttps://github.com/ocaml/opam-repository/tree/master/packages/conduit/conduit.0.14.4/opam

Network connection library for TCP and SSL

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 (either OpenSSL or a native OCaml TLS implementation).

If you are using the Lwt_unix version of the library, you can set two environment variables to control the behaviour of the library:

  • CONDUIT_DEBUG=1 will output debug information to standard error.
  • CONDUIT_TLS=native will force the use of the pure OCaml TLS library.