package paf
HTTP/AF and MirageOS
Install
Dune Dependency
Authors
Maintainers
Sources
paf-0.5.0.tbz
sha256=a1646fc1bf0386d17796d59a67a9a82a681a74552782bba8d54388686355fe83
sha512=616f5b7c7090b5f9bba70969fce56ffc909ec31a6a9045d8093e4494e76607b4ebb957cc1b2318364d50f30e5414d058af46a23bf8ea0a0ee421dc94378b9c31
doc/paf.mirage/Paf_mirage/index.html
Module Paf_mirageSource
Source
module Make
(Stack : Tcpip.Tcp.S) :
S with type stack = Stack.t and type ipaddr = Stack.ipaddrClient implementation.
The client implementation of Paf_mirage does not strictly need a functor. Indeed, the client was made in the sense of mimic. The user should provide a Mimic.ctx which generate a paf_transmission. By this way, the run function is able to introspect the used protocol (regardless its implementation) and do the ALPN challenge with the server.
Source
val run :
ctx:Mimic.ctx ->
(Ipaddr.t * int) option Alpn.client_handler ->
[ `V1 of Httpaf.Request.t | `V2 of H2.Request.t ] ->
(Alpn.alpn_response, [> Mimic.error ]) result Lwt.trun ~ctx handler req sends an HTTP request (H2 or HTTP/1.1) to a peer which can be reached via the given Mimic's ctx. If the connection is recognized as a tls_protocol, we proceed an ALPN challenge between what the user chosen and what the peer can handle. Otherwise, we send a simple HTTP/1.1 request or a h2c request.
On This Page