wasi:io/error@0.2.0-rc-2023-11-10wasi:io/poll@0.2.0-rc-2023-11-10wasi:io/streams@0.2.0-rc-2023-11-10wasi:cli/stdout@0.2.0-rc-2023-11-10wasi:cli/stderr@0.2.0-rc-2023-11-10wasi:cli/stdin@0.2.0-rc-2023-11-10wasi:cli/stdout@0.2.0-rc-2023-12-05wasi:cli/stderr@0.2.0-rc-2023-12-05wasi:cli/stdin@0.2.0-rc-2023-12-05wasi:clocks/monotonic-clock@0.2.0-rc-2023-11-10wasi:http/types@0.2.0-rc-2023-11-10wasi:http/outgoing-handler@0.2.0-rc-2023-11-10wasi:http/types@0.2.0-rc-2023-12-05wasi:http/outgoing-handler@0.2.0-rc-2023-12-05wasi:clocks/wall-clock@0.2.0-rc-2023-11-10wasi:http/incoming-handler@0.2.0-rc-2023-11-10wasi:http/incoming-handler@0.2.0-rc-2023-12-05u64.
resource errorA resource which represents some error information.
+The only method provided by this resource is to-debug-string,
+which provides some human-readable information about the error.
In the wasi:io package, this resource is returned through the
+wasi:io/streams/stream-error type.
To provide more specific error information, other interfaces may
+provide functions to further "downcast" this error into more specific
+error information. For example, errors returned in streams derived
+from filesystem types to be described using the filesystem's own
+error-code type, using the function
+wasi:filesystem/types/filesystem-error-code, which takes a parameter
+borrow<error> and returns
+option<wasi:filesystem/types/error-code>.
error into a more
+concrete type is open.[method]error.to-debug-string: funcReturns a string that is suitable to assist humans in debugging @@ -85,7 +99,7 @@ at once.
resource pollablepollable represents a single I/O event which may be ready, or not.[method]pollable.ready: funcReturn the readiness of a pollable. This function never blocks.
@@ -159,8 +173,21 @@ future operations.resource input-streamAn input bytestream.
+input-streams are non-blocking to the extent practical on underlying
+platforms. I/O operations always return promptly; if fewer bytes are
+promptly available than requested, they return the number of bytes promptly
+available, which could even be zero. To wait for data to be available,
+use the subscribe function to obtain a pollable which can be polled
+for using wasi:io/poll.
resource output-streamAn output bytestream.
+output-streams are non-blocking to the extent practical on
+underlying platforms. Except where specified otherwise, I/O operations also
+always return promptly, after the number of bytes that can be written
+promptly, which could even be zero. To wait for the stream to be ready to
+accept data, the subscribe function to obtain a pollable which can be
+polled for using wasi:io/poll.[method]input-stream.read: funcPerform a non-blocking read from the stream.
@@ -281,7 +308,7 @@ following pseudo-code:let pollable = this.subscribe();
while !contents.is_empty() {
// Wait for the stream to become writable
- poll-one(pollable);
+ pollable.block();
let Ok(n) = this.check-write(); // eliding error handling
let len = min(n, contents.len());
let (chunk, rest) = contents.split_at(len);
@@ -290,7 +317,7 @@ while !contents.is_empty() {
}
this.flush();
// Wait for completion of `flush`
-poll-one(pollable);
+pollable.block();
// Check for any errors that arose during `flush`
let _ = this.check-write(); // eliding error handling
pollables created with this fun
[method]output-stream.write-zeroes: funcWrite zeroes to a stream.
-this should be used precisely like write with the exact same
+
This should be used precisely like write with the exact same
preconditions (must use check-write first), but instead of
passing a list of bytes, you simply pass the number of zero-bytes
that should be written.
let pollable = this.subscribe();
while num_zeroes != 0 {
// Wait for the stream to become writable
- poll-one(pollable);
+ pollable.block();
let Ok(n) = this.check-write(); // eliding error handling
let len = min(n, num_zeroes);
this.write-zeroes(len); // eliding error handling
@@ -381,7 +408,7 @@ while num_zeroes != 0 {
}
this.flush();
// Wait for completion of `flush`
-poll-one(pollable);
+pollable.block();
// Check for any errors that arose during `flush`
let _ = this.check-write(); // eliding error handling
splice.
u64, stream-error>type output-streamsplice.
output-stream>type output-streamsplice.
output-stream>type input-streampollable>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.
@@ -678,6 +705,15 @@ permitted because the fields are immutable. reality, HTTP implementations often have to interpret malformed values, so they are provided as a list of bytes.resource fieldsThis following block defines the fields resource which corresponds to
+HTTP standard Fields. Fields are a common representation used for both
+Headers and Trailers.
A fields may be mutable or immutable. A fields created using the
+constructor, from-list, or clone will be mutable, but a fields
+resource given by other means (including, but not limited to,
+incoming-request.headers, outgoing-request.headers) might be be
+immutable. In an immutable fields, the set, append, and delete
+operations will fail with header-error.immutable.
type headersHeaders is an alias for Fields. @@ -685,19 +721,60 @@ so they are provided as a list of bytes.
Trailers is an alias for Fields.
resource incoming-requestRepresents an incoming HTTP Request.
resource outgoing-requestRepresents an outgoing HTTP Request.
resource request-optionsParameters for making an HTTP Request. Each of these parameters is +currently an optional timeout applicable to the transport layer of the +HTTP protocol.
+These timeouts are separate from any the user may use to bound a
+blocking call to wasi:io/poll.poll.
resource response-outparamRepresents the ability to send an HTTP Response.
+This resource is used by the wasi:http/incoming-handler interface to
+allow a Response to be sent corresponding to the Request provided as the
+other argument to incoming-handler.handle.
type status-codeu16
This type corresponds to the HTTP standard Status Code.
resource incoming-responseRepresents an incoming HTTP Response.
resource incoming-bodyRepresents an incoming HTTP Request or Response's Body.
+A body has both its contents - a stream of bytes - and a (possibly
+empty) set of trailers, indicating that the full contents of the
+body have been received. This resource represents the contents as
+an input-stream and the delivery of trailers as a future-trailers,
+and ensures that the user of this interface may only be consuming either
+the body contents or waiting on trailers at any given time.
resource future-trailersRepresents a future which may eventaully return trailers, or an error.
+In the case that the incoming HTTP Request or Response did not have any +trailers, this future will resolve to the empty set of trailers once the +complete Request or Response body has been received.
resource outgoing-responseRepresents an outgoing HTTP Response.
resource outgoing-bodyRepresents an outgoing HTTP Request or Response's Body.
+A body has both its contents - a stream of bytes - and a (possibly
+empty) set of trailers, inducating the full contents of the body
+have been sent. This resource represents the contents as an
+output-stream child resource, and the completion of the body (with
+optional trailers) with a static function that consumes the
+outgoing-body resource, and ensures that the user of this interface
+may not write to the body contents after the body has been finished.
If the user code drops this resource, as opposed to calling the static
+method finish, the implementation should treat the body as incomplete,
+and that an error has occured. The implementation should propogate this
+error to the HTTP protocol by whatever means it has available,
+including: corrupting the body on the wire, aborting the associated
+Request, or sending a late status code for the Response.
resource future-incoming-responseRepresents a future which may eventaully return an incoming HTTP +Response, or an error.
+wasi:http/outgoing-handler interface to
+provide the HTTP Response corresponding to the sent Request.http-error-code: funcAttempts to extract a http-related error from the wasi:io error
@@ -1368,7 +1445,7 @@ but those will be reported by the incoming-body
>, incoming-responseerror-code>>>
-
This interface defines a handler of outgoing HTTP Requests. It should be imported by components which wish to make HTTP Requests.
datetimetype incoming-request