Page
Library
Module
Module type
Parameter
Class
Class type
Source
Mirage_flow_combinators.FSourceIn-memory, function-based flows.
include Mirage_flow.SThe type for flow errors.
The type for write errors.
pp_write_error is the pretty-printer for write errors.
The type for flows. A flow represents the state of a single reliable stream that is connected to an endpoint.
read flow blocks until some data is available and returns a fresh buffer containing it.
The returned buffer will be of a size convenient to the flow implementation, but will always have at least 1 byte.
If the remote endpoint calls close then calls to read will keep returning data until all the in-flight data has been read. read flow will return `Eof when the remote endpoint has called close and when there is no more in-flight data.
write flow buffer writes a buffer to the flow. There is no indication when the buffer has actually been read and, therefore, it must not be reused. The contents may be transmitted in separate packets, depending on the underlying transport. The result Ok () indicates success, Error `Closed indicates that the connection is now closed and therefore the data could not be written. Other errors are possible.
writev flow buffers writes a sequence of buffers to the flow. There is no indication when the buffers have actually been read and, therefore, they must not be reused. The result Ok () indicates success, Error `Closed indicates that the connection is now closed and therefore the data could not be written. Other errors are possible.
close flow flushes all pending writes and signals the remote endpoint that there will be no future writes. Once the remote endpoint has read all pending data, it is expected that calls to read on the remote return `Eof.
Note it is still possible for the remote endpoint to write to the flow and for the local endpoint to call read. This state where the local endpoint has called close but the remote endpoint has not called close is similar to that of a half-closed TCP connection or a Unix socket after shutdown(SHUTDOWN_WRITE).
close flow waits until the remote endpoint has also called close before returning. At this point no data can flow in either direction and resources associated with the flow can be freed.
make ~close ~input ~output () is a flow using input to refill its internal input buffer when needed and output to refill its external output buffer. It is using close to eventually clean-up other resources on close.
input_string buf is the refill function reading its inputs from the string buf.
output_bytes buf is the refill function writing its outputs in the buffer buf.
The flow built using input_string and output_bytes.
input_strings bufs is the refill function reading its inputs from the list of buffers bufs. Empty strings are ignored.
output_bytess buf is the refill function writing its outputs in the list of buffers buf. Empty strings are ignored.
The flow built using input_strings and output_bytess.
Same as input_string but for Cstruct.t buffers.
Same as output_string buf for Cstruct.t buffers.
Same as input_strings but for Cstruct.t buffers.
Same as output_strings but for Cstruct.t buffers.