v0.2.4 · Interface
types
This interface defines all of the types and methods for implementing HTTP Requests and Responses, both incoming and outgoing, as well as their headers, trailers, and bodies.
Resources
R
fields
RThis following block defines the <code>fields</code> resource which corresponds to
incoming-request
RRepresents an incoming HTTP Request.
outgoing-request
RRepresents an outgoing HTTP Request.
request-options
RParameters for making an HTTP Request. Each of these parameters is
response-outparam
RRepresents the ability to send an HTTP Response.
incoming-response
RRepresents an incoming HTTP Response.
incoming-body
RRepresents an incoming HTTP Request or Response's Body.
future-trailers
RRepresents a future which may eventually return trailers, or an error.
outgoing-response
RRepresents an outgoing HTTP Response.
outgoing-body
RRepresents an outgoing HTTP Request or Response's Body.
future-incoming-response
Represents a future which may eventually return an incoming HTTP
Type Aliases
T
duration
TA duration of time, in nanoseconds.
input-stream
TAn input bytestream.
output-stream
TAn output bytestream.
io-error
TA resource which represents some error information.
pollable
T<code>pollable</code> represents a single I/O event which may be ready, or not.
field-key
TField keys are always strings.
field-name
TField names are always strings.
field-value
TField values should always be ASCII strings. However, in
headers
THeaders is an alias for Fields.
trailers
TTrailers is an alias for Fields.
status-code
This type corresponds to the HTTP standard Status Code.