package paf
HTTP/AF and MirageOS
Install
Dune Dependency
Authors
Maintainers
Sources
paf-0.7.0.tbz
sha256=c36946b3e0d8634f0150aba6585c4f1532d02af7513eeec7d457503888c34321
sha512=b72e79ca5c32f7d7b5134417c685f02215e22375c324d7de1d1534e02d75f60a7efdd31c4189176a65f02ead0dcc4eec33ea83e9690c7b0a31ea26aaf12b98e4
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