package mirage-conduit

  1. Overview
  2. Docs
An OCaml network connection establishment library

Install

Dune Dependency

Authors

Maintainers

Sources

conduit-1.0.3.tbz
sha256=4b6f4bef5262a898ea919137267b844ff5a29f6e3ce95a71c4f0d5b85138abdd
md5=e1ec0cbd3478ea572f43491fab69db44

Description

Build Status

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

  • API Docs: http://docs.mirage.io/
  • WWW: https://github.com/mirage/ocaml-conduit
  • E-mail: mirageos-devel@lists.xenproject.org
  • Bugs: https://github.com/mirage/ocaml-conduit/issues

Tags

org:mirage

Published: 07 Jan 2018

README

conduit -- an OCaml network connection establishment library

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

Dependencies (12)

  1. tls >= "0.8.0" & < "0.11.0"
  2. xenstore
  3. vchan >= "3.0.0"
  4. conduit-lwt
  5. mirage-dns >= "3.0.0" & < "4.0.0"
  6. mirage-flow-lwt >= "1.2.0"
  7. mirage-types-lwt >= "3.0.0" & < "3.7.0"
  8. cstruct >= "3.0.0"
  9. ppx_sexp_conv
  10. ipaddr < "3.0.0"
  11. jbuilder >= "1.0+beta9"
  12. ocaml >= "4.03.0"

Dev Dependencies

None

Used by (2)

  1. h2-mirage != "0.2.0" & < "0.4.0"
  2. mirage-http >= "2.1.0" & < "2.3.0"

Conflicts

None

OCaml

Innovation. Community. Security.