package websocket-lwt-unix

Build not yet checked
  1. Overview
  2. No Docs
Websocket library (Lwt)

Install

dune-project
 Dependency

Authors

Maintainers

Sources

websocket-2.18.tbz
sha256=d36994a7cdc693eae04d80a09f47e3e42482bdfb1576e0d925a896c7961ba096
sha512=6e0071767dee97a6e4c5441e3b89db18b07447fcfe436e8d0dc202fe5cc6d4b3a68eb748c42b8ed26fe73caaef784005e5481b4bdb41bf1d75caf38890d0c4f0

Description

The WebSocket Protocol enables two-way communication between a client running untrusted code in a controlled environment to a remote host that has opted-in to communications from that code.

The security model used for this is the origin-based security model commonly used by web browsers. The protocol consists of an opening handshake followed by basic message framing, layered over TCP.

The goal of this technology is to provide a mechanism for browser-based applications that need two-way communication with servers that does not rely on opening multiple HTTP connections (e.g., using XMLHttpRequest or s and long polling).

Tags

org:mirage org:xapi-project

Added to opam-repository:

Dependencies (9)

  1. sexplib
  2. mirage-crypto-rng >= "1.2.0"
  3. cohttp-lwt-unix >= "6.0.0"
  4. conduit-lwt-unix
  5. lwt >= "5.7.0"
  6. logs >= "0.8.0"
  7. websocket = version
  8. ocaml >= "4.08"
  9. dune >= "2.9"

Dev Dependencies (1)

  1. odoc with-doc

Optional Dependencies

None

Conflicts

None

Build status

Results of building websocket-lwt-unix with each compiler on check.ci.ocaml.org, run of against opam-repository 8a77e58. All results for this package.

Each result links to its build log. To keep crawlers from overloading the site, build logs require a GitHub sign-in (see ocurrent/opam-health-check). On your first log, GitHub asks you to “Authorize opam-health-check”, the OCurrent app that runs these checks; it sees only your public profile, not your repositories. The sign-in lasts 30 days.

This version is not in the latest run; the versions below are.

Version OCaml 4.11 OCaml 4.14 OCaml 5.2 OCaml 5.4 OCaml 5.5
2.17 n/a good good good good
2.16 good good good good good
  • good Package successfully built
  • partial One of the dependencies failed to build
  • bad Package failed to build
  • n/a Package is not available in this environment
  • internal Internal failure