package paf
HTTP/AF and MirageOS
Install
Dune Dependency
Authors
Maintainers
Sources
paf-0.6.0.tbz
sha256=baf35eceec745789b06f1534ef309f0985ce80260a3f1b2138a8a20232de7fd9
sha512=5d359537b27571f1ad407722f05d2d1fae9bfa104e235fc1f9dfddb9215cbf1ddf5c983860ba8f3d73f172490b33466ff228deee840cd472c3031fe17b921bd2
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