package named-pipe
Bindings for named pipes
Install
Dune Dependency
Authors
Maintainers
Sources
named-pipe-0.4.0.tbz
sha256=c602f4d5fdc9f5ff8ec83a0d43608ad76f49f50c4b4bf10774435e7ed8688374
md5=ec3a7aaec3cc0efd6560dd1668da6def
Description
Named pipes are used on Windows for local (and remote) IPC. Where a Unix system would use a Unix domain socket, a Windows system will probably used a named pipe.
Published: 10 Nov 2016
README
OCaml bindings for named pipes
Named pipes are used on Windows for local (and remote) IPC. Where a Unix system would use a Unix domain socket, a Windows system will probably used a named pipe.
Example
To build:
oasis setup
make
To run a server:
./_build/src/pipecat.native -l \\\\.\\pipe\\mynamedpipe
To run a client:
./_build/src/pipecat.native \\\\.\\pipe\\mynamedpipe
Notes
Named pipes have a number of significant differences to Unix domain sockets to be careful. These bindings attempt to disable remote connections and disable security context impersonation but there may be other issues.
Dependencies (9)
- cmdliner
- base-unix
-
lwt
>= "2.4.7" & < "5.0.0"
- base-bytes
-
ocb-stubblr
build & >= "0.1.0"
-
topkg
build & >= "0.8.1"
-
ocamlbuild
build & >= "0.9.3"
-
ocamlfind
build
-
ocaml
>= "3.12.1"
Dev Dependencies (1)
-
alcotest
with-test & >= "0.4.0"
Used by (5)
- datakit
-
datakit-github
< "0.9.0"
-
protocol-9p
= "0.5.2" | >= "0.7.2" & < "0.12.1"
-
protocol-9p-unix
< "0.12.1"
-
vpnkit
< "0.2.0"
Conflicts
None
sectionYPositions = computeSectionYPositions($el), 10)"
x-init="setTimeout(() => sectionYPositions = computeSectionYPositions($el), 10)"
>
On This Page