The messaging-service
world is a world that exports a single
asyncrhonous messaging handler that can be used to
handle incoming messages from some message broker provider,
and a set of capabilities that can be used to interact with
the platform / runtime.
- Imports:
- interface
wasi:keyvalue/[email protected]
- interface
wasi:keyvalue/[email protected]
- interface
wasi:keyvalue/[email protected]
- interface
wasi:io/[email protected]
- interface
wasi:io/[email protected]
- interface
wasi:io/[email protected]
- interface
wasi:blobstore/[email protected]
- interface
wasi:blobstore/[email protected]
- interface
wasi:blobstore/[email protected]
- interface
wasi:messaging/[email protected]
- interface
wasi:messaging/[email protected]
- interface
wasi:messaging/[email protected]
- interface
wasi:config/[email protected]
- interface
wasi:clocks/[email protected]
- interface
wasi:clocks/[email protected]
- interface
wasi:random/[email protected]
- interface
wasi:cli/[email protected]
- interface
wasi:cli/[email protected]
- interface
wasi:cli/[email protected]
- interface
wasi:http/[email protected]
- interface
wasi:http/[email protected]
- interface
- Exports:
- interface
wasi:messaging/[email protected]
- interface
Import interface wasi:keyvalue/[email protected]
A keyvalue interface that provides eventually consistent key-value operations.
Each of these operations acts on a single key-value pair.
The value in the key-value pair is defined as a u8
byte array and the intention is that it is
the common denominator for all data types defined by different key-value stores to handle data,
ensuring compatibility between different key-value stores. Note: the clients will be expecting
serialization/deserialization overhead to be handled by the key-value store. The value could be
a serialized object from JSON, HTML or vendor-specific data types like AWS S3 objects.
Data consistency in a key value store refers to the guarantee that once a write operation completes, all subsequent read operations will return the value that was written.
Any implementation of this interface must have enough consistency to guarantee "reading your writes." In particular, this means that the client should never get a value that is older than the one it wrote, but it MAY get a newer value if one was written around the same time. These guarantees only apply to the same client (which will likely be provided by the host or an external capability of some kind). In this context a "client" is referring to the caller or guest that is consuming this interface. Once a write request is committed by a specific client, all subsequent read requests by the same client will reflect that write or any subsequent writes. Another client running in a different context may or may not immediately see the result due to the replication lag. As an example of all of this, if a value at a given key is A, and the client writes B, then immediately reads, it should get B. If something else writes C in quick succession, then the client may get C. However, a client running in a separate context may still see A or B
The set of errors which may be raised by functions in this package
-
The host does not recognize the store identifier requested.
-
The requesting component does not have access to the specified store (which may or may not exist).
-
Some implementation-specific error has occurred (e.g. I/O)
A response to a list-keys
operation.
-
The list of keys returned by the query.
-
The continuation token to use to fetch the next page of keys. If this is `null`, then there are no more keys to fetch.
A bucket is a collection of key-value pairs. Each key-value pair is stored as a entry in the bucket, and the bucket itself acts as a collection of all these entries.
It is worth noting that the exact terminology for bucket in key-value stores can very depending on the specific implementation. For example:
- Amazon DynamoDB calls a collection of key-value pairs a table
- Redis has hashes, sets, and sorted sets as different types of collections
- Cassandra calls a collection of key-value pairs a column family
- MongoDB calls a collection of key-value pairs a collection
- Riak calls a collection of key-value pairs a bucket
- Memcached calls a collection of key-value pairs a slab
- Azure Cosmos DB calls a collection of key-value pairs a container
In this interface, we use the term bucket
to refer to a collection of key-value pairs
Get the bucket with the specified identifier.
identifier
must refer to a bucket provided by the host.
error::no-such-store
will be raised if the identifier
is not recognized.
Get the value associated with the specified key
The value is returned as an option. If the key-value pair exists in the
store, it returns Ok(value)
. If the key does not exist in the
store, it returns Ok(none)
.
If any other error occurs, it returns an Err(error)
.
self
: borrow<bucket
>key
:string
- result<option<list<
u8
>>,error
>
Set the value associated with the key in the store. If the key already exists in the store, it overwrites the value.
If the key does not exist in the store, it creates a new key-value pair.
If any other error occurs, it returns an Err(error)
.
self
: borrow<bucket
>key
:string
value
: list<u8
>
- result<_,
error
>
Delete the key-value pair associated with the key in the store.
If the key does not exist in the store, it does nothing.
If any other error occurs, it returns an Err(error)
.
self
: borrow<bucket
>key
:string
- result<_,
error
>
Check if the key exists in the store.
If the key exists in the store, it returns Ok(true)
. If the key does
not exist in the store, it returns Ok(false)
.
If any other error occurs, it returns an Err(error)
.
self
: borrow<bucket
>key
:string
- result<
bool
,error
>
Get all the keys in the store with an optional cursor (for use in pagination). It
returns a list of keys. Please note that for most KeyValue implementations, this is a
can be a very expensive operation and so it should be used judiciously. Implementations
can return any number of keys in a single response, but they should never attempt to
send more data than is reasonable (i.e. on a small edge device, this may only be a few
KB, while on a large machine this could be several MB). Any response should also return
a cursor that can be used to fetch the next page of keys. See the key-response
record
for more information.
Note that the keys are not guaranteed to be returned in any particular order.
If the store is empty, it returns an empty list.
MAY show an out-of-date list of keys if there are concurrent writes to the store.
If any error occurs, it returns an Err(error)
.
self
: borrow<bucket
>cursor
: option<string
>
- result<
key-response
,error
>
Import interface wasi:keyvalue/[email protected]
A keyvalue interface that provides atomic operations.
Atomic operations are single, indivisible operations. When a fault causes an atomic operation to fail, it will appear to the invoker of the atomic operation that the action either completed successfully or did nothing at all.
Please note that this interface is bare functions that take a reference to a bucket. This is to
get around the current lack of a way to "extend" a resource with additional methods inside of
wit. Future version of the interface will instead extend these methods on the base bucket
resource.
#### `type error` [`error`](#error)
A handle to a CAS (compare-and-swap) operation.
The error returned by a CAS operation
-
store-error
:error
A store error occurred when performing the operation
-
cas-failed
: own<cas
>The CAS operation failed because the value was too old. This returns a new CAS handle for easy retries. Implementors MUST return a CAS handle that has been updated to the latest version or transaction.
Construct a new CAS operation. Implementors can map the underlying functionality (transactions, versions, etc) as desired.
Get the current value of the key (if it exists). This allows for avoiding reads if all that is needed to ensure the atomicity of the operation
self
: borrow<cas
>
- result<option<list<
u8
>>,error
>
Atomically increment the value associated with the key in the store by the given delta. It returns the new value.
If the key does not exist in the store, it creates a new key-value pair with the value set to the given delta.
If any other error occurs, it returns an Err(error)
.
- result<
s64
,error
>
Perform the swap on a CAS operation. This consumes the CAS handle and returns an error if the CAS operation failed.
- result<_,
cas-error
>
Import interface wasi:keyvalue/[email protected]
A keyvalue interface that provides batch operations.
A batch operation is an operation that operates on multiple keys at once.
Batch operations are useful for reducing network round-trip time. For example, if you want to get the values associated with 100 keys, you can either do 100 get operations or you can do 1 batch get operation. The batch operation is faster because it only needs to make 1 network call instead of 100.
A batch operation does not guarantee atomicity, meaning that if the batch operation fails, some of the keys may have been modified and some may not.
This interface does has the same consistency guarantees as the store
interface, meaning that
you should be able to "read your writes."
Please note that this interface is bare functions that take a reference to a bucket. This is to
get around the current lack of a way to "extend" a resource with additional methods inside of
wit. Future version of the interface will instead extend these methods on the base bucket
resource.
#### `type error` [`error`](#error)
----
Get the key-value pairs associated with the keys in the store. It returns a list of key-value pairs.
If any of the keys do not exist in the store, it returns a none
value for that pair in the
list.
MAY show an out-of-date value if there are concurrent writes to the store.
If any other error occurs, it returns an Err(error)
.
- result<list<option<(
string
, list<u8
>)>>,error
>
Set the values associated with the keys in the store. If the key already exists in the store, it overwrites the value.
Note that the key-value pairs are not guaranteed to be set in the order they are provided.
If any of the keys do not exist in the store, it creates a new key-value pair.
If any other error occurs, it returns an Err(error)
. When an error occurs, it does not
rollback the key-value pairs that were already set. Thus, this batch operation does not
guarantee atomicity, implying that some key-value pairs could be set while others might
fail.
Other concurrent operations may also be able to see the partial results.
- result<_,
error
>
Delete the key-value pairs associated with the keys in the store.
Note that the key-value pairs are not guaranteed to be deleted in the order they are provided.
If any of the keys do not exist in the store, it skips the key.
If any other error occurs, it returns an Err(error)
. When an error occurs, it does not
rollback the key-value pairs that were already deleted. Thus, this batch operation does not
guarantee atomicity, implying that some key-value pairs could be deleted while others might
fail.
Other concurrent operations may also be able to see the partial results.
- result<_,
error
>
Import interface wasi:io/[email protected]
A 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
offer functions to "downcast" this error into more specific types. For example,
errors returned from streams derived from filesystem types can be described using
the filesystem's own error-code type. This is done using the function
wasi:filesystem/types/filesystem-error-code
, which takes a borrow<error>
parameter and returns an option<wasi:filesystem/types/error-code>
.
The set of functions which can "downcast" an error
into a more
concrete type is open.
Returns a string that is suitable to assist humans in debugging this error.
WARNING: The returned string should not be consumed mechanically! It may change across platforms, hosts, or other implementation details. Parsing this string is a major platform-compatibility hazard.
self
: borrow<error
>
Import interface wasi:io/[email protected]
A poll API intended to let users wait for I/O events on multiple handles at once.
pollable
represents a single I/O event which may be ready, or not.
Return the readiness of a pollable. This function never blocks.
Returns true
when the pollable is ready, and false
otherwise.
self
: borrow<pollable
>
block
returns immediately if the pollable is ready, and otherwise
blocks until ready.
This function is equivalent to calling poll.poll
on a list
containing only this pollable.
self
: borrow<pollable
>
Poll for completion on a set of pollables.
This function takes a list of pollables, which identify I/O sources of interest, and waits until one or more of the events is ready for I/O.
The result list<u32>
contains one or more indices of handles in the
argument list that is ready for I/O.
This function traps if either:
- the list is empty, or:
- the list contains more elements than can be indexed with a
u32
value.
A timeout can be implemented by adding a pollable from the wasi-clocks API to the list.
This function does not return a result
; polling in itself does not
do any I/O so it doesn't fail. If any of the I/O sources identified by
the pollables has an error, it is indicated by marking the source as
being ready for I/O.
in
: list<borrow<pollable
>>
Import interface wasi:io/[email protected]
WASI I/O is an I/O abstraction API which is currently focused on providing stream types.
In the future, the component model is expected to add built-in stream types; when it does, they are expected to subsume this API.
#### `type pollable` [`pollable`](#pollable)
An error for input-stream and output-stream operations.
-
last-operation-failed
: own<error
>The last operation (a write or flush) failed before completion.
More information is available in the
error
payload.After this, the stream will be closed. All future operations return
stream-error::closed
. -
The stream is closed: no more input will be accepted by the stream. A closed output-stream will return this error on all future operations.
An input bytestream.
input-stream
s 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
.
An output bytestream.
output-stream
s 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
.
Dropping an output-stream
while there's still an active write in
progress may result in the data being lost. Before dropping the stream,
be sure to fully flush your writes.
Perform a non-blocking read from the stream.
When the source of a read
is binary data, the bytes from the source
are returned verbatim. When the source of a read
is known to the
implementation to be text, bytes containing the UTF-8 encoding of the
text are returned.
This function returns a list of bytes containing the read data,
when successful. The returned list will contain up to len
bytes;
it may return fewer than requested, but not more. The list is
empty when no bytes are available for reading at this time. The
pollable given by subscribe
will be ready when more bytes are
available.
This function fails with a stream-error
when the operation
encounters an error, giving last-operation-failed
, or when the
stream is closed, giving closed
.
When the caller gives a len
of 0, it represents a request to
read 0 bytes. If the stream is still open, this call should
succeed and return an empty list, or otherwise fail with closed
.
The len
parameter is a u64
, which could represent a list of u8 which
is not possible to allocate in wasm32, or not desirable to allocate as
as a return value by the callee. The callee may return a list of bytes
less than len
in size while more bytes are available for reading.
self
: borrow<input-stream
>len
:u64
- result<list<
u8
>,stream-error
>
Read bytes from a stream, after blocking until at least one byte can
be read. Except for blocking, behavior is identical to read
.
self
: borrow<input-stream
>len
:u64
- result<list<
u8
>,stream-error
>
Skip bytes from a stream. Returns number of bytes skipped.
Behaves identical to read
, except instead of returning a list
of bytes, returns the number of bytes consumed from the stream.
self
: borrow<input-stream
>len
:u64
- result<
u64
,stream-error
>
Skip bytes from a stream, after blocking until at least one byte
can be skipped. Except for blocking behavior, identical to skip
.
self
: borrow<input-stream
>len
:u64
- result<
u64
,stream-error
>
Create a pollable
which will resolve once either the specified stream
has bytes available to read or the other end of the stream has been
closed.
The created pollable
is a child resource of the input-stream
.
Implementations may trap if the input-stream
is dropped before
all derived pollable
s created with this function are dropped.
self
: borrow<input-stream
>
- own<
pollable
>
Check readiness for writing. This function never blocks.
Returns the number of bytes permitted for the next call to write
,
or an error. Calling write
with more bytes than this function has
permitted will trap.
When this function returns 0 bytes, the subscribe
pollable will
become ready when this function will report at least 1 byte, or an
error.
self
: borrow<output-stream
>
- result<
u64
,stream-error
>
Perform a write. This function never blocks.
When the destination of a write
is binary data, the bytes from
contents
are written verbatim. When the destination of a write
is
known to the implementation to be text, the bytes of contents
are
transcoded from UTF-8 into the encoding of the destination and then
written.
Precondition: check-write gave permit of Ok(n) and contents has a length of less than or equal to n. Otherwise, this function will trap.
returns Err(closed) without writing if the stream has closed since the last call to check-write provided a permit.
self
: borrow<output-stream
>contents
: list<u8
>
- result<_,
stream-error
>
Perform a write of up to 4096 bytes, and then flush the stream. Block until all of these operations are complete, or an error occurs.
This is a convenience wrapper around the use of check-write
,
subscribe
, write
, and flush
, and is implemented with the
following pseudo-code:
let pollable = this.subscribe();
while !contents.is_empty() {
// Wait for the stream to become writable
pollable.block();
let Ok(n) = this.check-write(); // eliding error handling
let len = min(n, contents.len());
let (chunk, rest) = contents.split_at(len);
this.write(chunk ); // eliding error handling
contents = rest;
}
this.flush();
// Wait for completion of `flush`
pollable.block();
// Check for any errors that arose during `flush`
let _ = this.check-write(); // eliding error handling
self
: borrow<output-stream
>contents
: list<u8
>
- result<_,
stream-error
>
Request to flush buffered output. This function never blocks.
This tells the output-stream that the caller intends any buffered
output to be flushed. the output which is expected to be flushed
is all that has been passed to write
prior to this call.
Upon calling this function, the output-stream
will not accept any
writes (check-write
will return ok(0)
) until the flush has
completed. The subscribe
pollable will become ready when the
flush has completed and the stream can accept more writes.
self
: borrow<output-stream
>
- result<_,
stream-error
>
Request to flush buffered output, and block until flush completes and stream is ready for writing again.
self
: borrow<output-stream
>
- result<_,
stream-error
>
Create a pollable
which will resolve once the output-stream
is ready for more writing, or an error has occurred. When this
pollable is ready, check-write
will return ok(n)
with n>0, or an
error.
If the stream is closed, this pollable is always ready immediately.
The created pollable
is a child resource of the output-stream
.
Implementations may trap if the output-stream
is dropped before
all derived pollable
s created with this function are dropped.
self
: borrow<output-stream
>
- own<
pollable
>
Write zeroes to a stream.
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.
self
: borrow<output-stream
>len
:u64
- result<_,
stream-error
>
Perform a write of up to 4096 zeroes, and then flush the stream. Block until all of these operations are complete, or an error occurs.
This is a convenience wrapper around the use of check-write
,
subscribe
, write-zeroes
, and flush
, and is implemented with
the following pseudo-code:
let pollable = this.subscribe();
while num_zeroes != 0 {
// Wait for the stream to become writable
pollable.block();
let Ok(n) = this.check-write(); // eliding error handling
let len = min(n, num_zeroes);
this.write-zeroes(len); // eliding error handling
num_zeroes -= len;
}
this.flush();
// Wait for completion of `flush`
pollable.block();
// Check for any errors that arose during `flush`
let _ = this.check-write(); // eliding error handling
self
: borrow<output-stream
>len
:u64
- result<_,
stream-error
>
Read from one stream and write to another.
The behavior of splice is equivalent to:
- calling
check-write
on theoutput-stream
- calling
read
on theinput-stream
with the smaller of thecheck-write
permitted length and thelen
provided tosplice
- calling
write
on theoutput-stream
with that read data.
Any error reported by the call to check-write
, read
, or
write
ends the splice and reports that error.
This function returns the number of bytes transferred; it may be less
than len
.
self
: borrow<output-stream
>src
: borrow<input-stream
>len
:u64
- result<
u64
,stream-error
>
Read from one stream and write to another, with blocking.
This is similar to splice
, except that it blocks until the
output-stream
is ready for writing, and the input-stream
is ready for reading, before performing the splice
.
self
: borrow<output-stream
>src
: borrow<input-stream
>len
:u64
- result<
u64
,stream-error
>
Import interface wasi:blobstore/[email protected]
Types used by blobstore
#### `type output-stream` [`output-stream`](#output_stream)
#### `type container-name` `string`
name of a container, a collection of objects. The container name may be any valid UTF-8 string.
string
name of an object within a container The object name may be any valid UTF-8 string.
u64
TODO: define timestamp to include seconds since Unix epoch and nanoseconds WebAssembly/wasi-blobstore#7
u64
size of an object, in bytes
string
#### `record container-metadata`
information about a container
-
name
:container-name
the container's name
-
created-at
:timestamp
date and time container was created
information about an object
-
name
:object-name
the object's name
-
the object's parent container
-
created-at
:timestamp
date and time the object was created
-
size
:object-size
size of the object, in bytes
identifier for an object that includes its container name
container
:container-name
object
:object-name
A data is the data stored in a data blob. The value can be of any type
that can be represented in a byte array. It provides a way to write the value
to the output-stream defined in the wasi-io
interface.
Soon: switch to resource value { ... }
A incoming-value is a wrapper around a value. It provides a way to read the value
from the input-stream defined in the wasi-io
interface.
The incoming-value provides two ways to consume the value:
incoming-value-consume-sync
consumes the value synchronously and returns the value as a list of bytes.incoming-value-consume-async
consumes the value asynchronously and returns the value as an input-stream. Soon: switch toresource incoming-value { ... }
#### `type incoming-value-sync-body` [`incoming-value-sync-body`](#incoming_value_sync_body)
----
- own<
outgoing-value
>
Returns a stream for writing the value contents.
The returned output-stream
is a child resource: it must be dropped
before the parent outgoing-value
resource is dropped (or finished),
otherwise the outgoing-value
drop or finish
will trap.
Returns success on the first call: the output-stream
resource for
this outgoing-value
may be retrieved at most once. Subsequent calls
will return error.
self
: borrow<outgoing-value
>
- result<own<
output-stream
>>
Finalize an outgoing value. This must be
called to signal that the outgoing value is complete. If the outgoing-value
is dropped without calling outgoing-value.finalize
, the implementation
should treat the value as corrupted.
this
: own<outgoing-value
>
- result<_,
error
>
this
: own<incoming-value
>
- result<
incoming-value-sync-body
,error
>
this
: own<incoming-value
>
- result<own<
incoming-value-async-body
>,error
>
self
: borrow<incoming-value
>
Import interface wasi:blobstore/[email protected]
a Container is a collection of objects
#### `type output-stream` [`output-stream`](#output_stream)
#### `type container-metadata` [`container-metadata`](#container_metadata)
#### `type error` [`error`](#error)
#### `type incoming-value` [`incoming-value`](#incoming_value)
#### `type object-metadata` [`object-metadata`](#object_metadata)
#### `type object-name` [`object-name`](#object_name)
#### `type outgoing-value` [`outgoing-value`](#outgoing_value)
this defines the container
resource
this defines the stream-object-names
resource which is a representation of stream
returns container name
self
: borrow<container
>
- result<
string
,error
>
returns container metadata
self
: borrow<container
>
- result<
container-metadata
,error
>
retrieves an object or portion of an object, as a resource. Start and end offsets are inclusive. Once a data-blob resource has been created, the underlying bytes are held by the blobstore service for the lifetime of the data-blob resource, even if the object they came from is later deleted.
self
: borrow<container
>name
:object-name
start
:u64
end
:u64
- result<own<
incoming-value
>,error
>
creates or replaces an object with the data blob.
self
: borrow<container
>name
:object-name
data
: borrow<outgoing-value
>
- result<_,
error
>
returns list of objects in the container. Order is undefined.
self
: borrow<container
>
- result<own<
stream-object-names
>,error
>
deletes object. does not return error if object did not exist.
self
: borrow<container
>name
:object-name
- result<_,
error
>
deletes multiple objects in the container
self
: borrow<container
>names
: list<object-name
>
- result<_,
error
>
returns true if the object exists in this container
self
: borrow<container
>name
:object-name
- result<
bool
,error
>
returns metadata for the object
self
: borrow<container
>name
:object-name
- result<
object-metadata
,error
>
removes all objects within the container, leaving the container empty.
self
: borrow<container
>
- result<_,
error
>
reads the next number of objects from the stream
This function returns the list of objects read, and a boolean indicating if the end of the stream was reached.
self
: borrow<stream-object-names
>len
:u64
- result<(list<
object-name
>,bool
),error
>
skip the next number of objects in the stream
This function returns the number of objects skipped, and a boolean indicating if the end of the stream was reached.
self
: borrow<stream-object-names
>num
:u64
- result<(
u64
,bool
),error
>
Import interface wasi:blobstore/[email protected]
wasi-cloud Blobstore service definition
#### `type error` [`error`](#error)
#### `type container-name` [`container-name`](#container_name)
#### `type object-id` [`object-id`](#object_id)
----
creates a new empty container
name
:container-name
retrieves a container by name
name
:container-name
deletes a container and all objects within it
name
:container-name
- result<_,
error
>
returns true if the container exists
name
:container-name
- result<
bool
,error
>
copies (duplicates) an object, to the same or a different container. returns an error if the target container does not exist. overwrites destination object if it already existed.
- result<_,
error
>
moves or renames an object, to the same or a different container returns an error if the destination container does not exist. overwrites destination object if it already existed.
- result<_,
error
>
Import interface wasi:messaging/[email protected]
A connection to a message-exchange service (e.g., buffer, broker, etc.).
TODO(danbugs): This should be eventually extracted as an underlying type for other wasi-cloud-core interfaces.
string
There are two types of channels: - publish-subscribe channel, which is a broadcast channel, and - point-to-point channel, which is a unicast channel.
The interface doesn't highlight this difference in the type itself as that's uniquely a consumer issue.
Configuration includes a required list of channels the guest is subscribing to, and an optional list of extensions key-value pairs (e.g., partitions/offsets to read from in Kafka/EventHubs, QoS etc.).
channels
: list<channel
>extensions
: option<list<(string
,string
)>>
Format specification for messages
- more info: https://github.com/clemensv/spec/blob/registry-extensions/registry/spec.md#message-formats
- message metadata can further decorate w/ things like format version, and so on.
A message with a binary payload, a format specification, and decorative metadata.
data
: list<u8
>format
:format-spec
metadata
: option<list<(string
,string
)>>
Import interface wasi:messaging/[email protected]
#### `type channel` [`channel`](#channel)
#### `type message` [`message`](#message)
#### `type error` [`error`](#error)
----
- result<_, own<
error
>>
Import interface wasi:messaging/[email protected]
#### `type message` [`message`](#message)
#### `type channel` [`channel`](#channel)
#### `type error` [`error`](#error)
#### `type guest-configuration` [`guest-configuration`](#guest_configuration)
----
Blocking receive for t-milliseconds with ephemeral subscription – if no message is received, returns None
Blocking receive until message with ephemeral subscription
'Fit-all' type function for updating a guest's configuration – this could be useful for:
- unsubscribing from a channel,
- checkpointing,
- etc..
- result<_, own<
error
>>
A message can exist under several statuses: (1) available: the message is ready to be read, (2) acquired: the message has been sent to a consumer (but still exists in the queue), (3) accepted (result of complete-message): the message has been received and ACK-ed by a consumer and can be safely removed from the queue, (4) rejected (result of abandon-message): the message has been received and NACK-ed by a consumer, at which point it can be:
- deleted,
- sent to a dead-letter queue, or
- kept in the queue for further processing.
m
:message
- result<_, own<
error
>>
m
:message
- result<_, own<
error
>>
Import interface wasi:config/[email protected]
An error type that encapsulates the different errors that can occur fetching configuration values.
-
This indicates an error from an "upstream" config source. As this could be almost _anything_ (such as Vault, Kubernetes ConfigMaps, KeyValue buckets, etc), the error message is a string.
-
This indicates an error from an I/O operation. As this could be almost _anything_ (such as a file read, network connection, etc), the error message is a string. Depending on how this ends up being consumed, we may consider moving this to use the `wasi:io/error` type instead. For simplicity right now in supporting multiple implementations, it is being left as a string.
Gets a configuration value of type string
associated with the key
.
The value is returned as an option<string>
. If the key is not found,
Ok(none)
is returned. If an error occurs, an Err(error)
is returned.
- result<option<
string
>,error
>
Gets a list of configuration key-value pairs of type string
.
If an error occurs, an Err(error)
is returned.
- result<list<(
string
,string
)>,error
>
Import interface wasi:clocks/[email protected]
WASI Monotonic Clock is a clock API intended to let users measure elapsed time.
It is intended to be portable at least between Unix-family platforms and Windows.
A monotonic clock is a clock which has an unspecified initial value, and successive reads of the clock will produce non-decreasing values.
An instant in time, in nanoseconds. An instant is relative to an unspecified initial value, and can only be compared to instances from the same monotonic-clock.
u64
A duration of time, in nanoseconds.
Read the current value of the clock.
The clock is monotonic, therefore calling this function repeatedly will produce a sequence of non-decreasing values.
Query the resolution of the clock. Returns the duration of time corresponding to a clock tick.
Create a pollable
which will resolve once the specified instant
has occurred.
when
:instant
- own<
pollable
>
Create a pollable
that will resolve after the specified duration has
elapsed from the time this function is invoked.
when
:duration
- own<
pollable
>
Import interface wasi:clocks/[email protected]
WASI Wall Clock is a clock API intended to let users query the current time. The name "wall" makes an analogy to a "clock on the wall", which is not necessarily monotonic as it may be reset.
It is intended to be portable at least between Unix-family platforms and Windows.
A wall clock is a clock which measures the date and time according to some external reference.
External references may be reset, so this clock is not necessarily monotonic, making it unsuitable for measuring elapsed time.
It is intended for reporting the current date and time for humans.
A time and date in seconds plus nanoseconds.
Read the current value of the clock.
This clock is not monotonic, therefore calling this function repeatedly will not necessarily produce a sequence of non-decreasing values.
The returned timestamps represent the number of seconds since 1970-01-01T00:00:00Z, also known as POSIX's Seconds Since the Epoch, also known as Unix Time.
The nanoseconds field of the output is always less than 1000000000.
Query the resolution of the clock.
The nanoseconds field of the output is always less than 1000000000.
Import interface wasi:random/[email protected]
WASI Random is a random data API.
It is intended to be portable at least between Unix-family platforms and Windows.
Return len
cryptographically-secure random or pseudo-random bytes.
This function must produce data at least as cryptographically secure and fast as an adequately seeded cryptographically-secure pseudo-random number generator (CSPRNG). It must not block, from the perspective of the calling program, under any circumstances, including on the first request and on requests for numbers of bytes. The returned data must always be unpredictable.
This function must always return fresh data. Deterministic environments must omit this function, rather than implementing it with deterministic data.
Return a cryptographically-secure random or pseudo-random u64
value.
This function returns the same type of data as get-random-bytes
,
represented as a u64
.
Import interface wasi:cli/[email protected]
----
- own<
output-stream
>
Import interface wasi:cli/[email protected]
----
- own<
output-stream
>
Import interface wasi:cli/[email protected]
----
- own<
input-stream
>
Import interface wasi:http/[email protected]
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.
#### `type input-stream` [`input-stream`](#input_stream)
#### `type output-stream` [`output-stream`](#output_stream)
#### `type io-error` [`error`](#error)
#### `type pollable` [`pollable`](#pollable)
This type corresponds to HTTP standard Methods.
get
head
post
put
delete
connect
options
trace
patch
other
:string
This type corresponds to HTTP standard Related Schemes.
Defines the case payload type for DNS-error
above:
Defines the case payload type for TLS-alert-received
above:
Defines the case payload type for HTTP-response-{header,trailer}-size
above:
field-name
: option<string
>field-size
: option<u32
>
These cases are inspired by the IANA HTTP Proxy Error Types: https://www.iana.org/assignments/http-proxy-status/http-proxy-status.xhtml#table-http-proxy-error-types
DNS-timeout
DNS-error
:DNS-error-payload
destination-not-found
destination-unavailable
destination-IP-prohibited
destination-IP-unroutable
connection-refused
connection-terminated
connection-timeout
connection-read-timeout
connection-write-timeout
connection-limit-reached
TLS-protocol-error
TLS-certificate-error
TLS-alert-received
:TLS-alert-received-payload
HTTP-request-denied
HTTP-request-length-required
HTTP-request-body-size
: option<u64
>HTTP-request-method-invalid
HTTP-request-URI-invalid
HTTP-request-URI-too-long
HTTP-request-header-section-size
: option<u32
>HTTP-request-header-size
: option<field-size-payload
>HTTP-request-trailer-section-size
: option<u32
>HTTP-request-trailer-size
:field-size-payload
HTTP-response-incomplete
HTTP-response-header-section-size
: option<u32
>HTTP-response-header-size
:field-size-payload
HTTP-response-body-size
: option<u64
>HTTP-response-trailer-section-size
: option<u32
>HTTP-response-trailer-size
:field-size-payload
HTTP-response-transfer-coding
: option<string
>HTTP-response-content-coding
: option<string
>HTTP-response-timeout
HTTP-upgrade-failed
HTTP-protocol-error
loop-detected
configuration-error
internal-error
: option<string
>This is a catch-all error for anything that doesn't fit cleanly into a more specific case. It also includes an optional string for an unstructured description of the error. Users should not depend on the string for diagnosing errors, as it's not required to be consistent between implementations.
This type enumerates the different kinds of errors that may occur when
setting or appending to a fields
resource.
-
This error indicates that a `field-name` or `field-value` was syntactically invalid when used with an operation that sets headers in a `fields`.
-
This error indicates that a forbidden `field-name` was used when trying to set a header in a `fields`.
-
This error indicates that the operation on the `fields` was not permitted because the fields are immutable.
string
Field keys are always strings.
Field keys should always be treated as case insensitive by the fields
resource for the purposes of equality checking.
This type has been deprecated in favor of the field-name
type.
Field names are always strings.
Field names should always be treated as case insensitive by the fields
resource for the purposes of equality checking.
Field values should always be ASCII strings. However, in reality, HTTP implementations often have to interpret malformed values, so they are provided as a list of bytes.
This 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
.
Headers is an alias for Fields.
Trailers is an alias for Fields.
Represents an incoming HTTP Request.
Represents an outgoing HTTP Request.
Parameters 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
.
Represents 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
.
u16
This type corresponds to the HTTP standard Status Code.
Represents an incoming HTTP Response.
Represents 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.
Represents a future which may eventually 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.
Represents an outgoing HTTP Response.
Represents 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 occurred. The implementation should propagate 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.
Represents a future which may eventually return an incoming HTTP Response, or an error.
This resource is returned by the wasi:http/outgoing-handler
interface to
provide the HTTP Response corresponding to the sent Request.
Attempts to extract a http-related error
from the wasi:io error
provided.
Stream operations which return
wasi:io/stream/stream-error::last-operation-failed
have a payload of
type wasi:io/error/error
with more information about the operation
that failed. This payload can be passed through to this function to see
if there's http-related information about the error to return.
Note that this function is fallible because not all io-errors are http-related errors.
err
: borrow<io-error
>
- option<
error-code
>
Construct an empty HTTP Fields.
The resulting fields
is mutable.
- own<
fields
>
Construct an HTTP Fields.
The resulting fields
is mutable.
The list represents each name-value pair in the Fields. Names which have multiple values are represented by multiple entries in this list with the same name.
The tuple is a pair of the field name, represented as a string, and Value, represented as a list of bytes.
An error result will be returned if any field-name
or field-value
is
syntactically invalid, or if a field is forbidden.
entries
: list<(field-name
,field-value
)>
- result<own<
fields
>,header-error
>
Get all of the values corresponding to a name. If the name is not present
in this fields
or is syntactically invalid, an empty list is returned.
However, if the name is present but empty, this is represented by a list
with one or more empty field-values present.
self
: borrow<fields
>name
:field-name
- list<
field-value
>
Returns true
when the name is present in this fields
. If the name is
syntactically invalid, false
is returned.
self
: borrow<fields
>name
:field-name
Set all of the values for a name. Clears any existing values for that name, if they have been set.
Fails with header-error.immutable
if the fields
are immutable.
Fails with header-error.invalid-syntax
if the field-name
or any of
the field-value
s are syntactically invalid.
self
: borrow<fields
>name
:field-name
value
: list<field-value
>
- result<_,
header-error
>
Delete all values for a name. Does nothing if no values for the name exist.
Fails with header-error.immutable
if the fields
are immutable.
Fails with header-error.invalid-syntax
if the field-name
is
syntactically invalid.
self
: borrow<fields
>name
:field-name
- result<_,
header-error
>
Append a value for a name. Does not change or delete any existing values for that name.
Fails with header-error.immutable
if the fields
are immutable.
Fails with header-error.invalid-syntax
if the field-name
or
field-value
are syntactically invalid.
self
: borrow<fields
>name
:field-name
value
:field-value
- result<_,
header-error
>
Retrieve the full set of names and values in the Fields. Like the constructor, the list represents each name-value pair.
The outer list represents each name-value pair in the Fields. Names which have multiple values are represented by multiple entries in this list with the same name.
The names and values are always returned in the original casing and in the order in which they will be serialized for transport.
self
: borrow<fields
>
- list<(
field-name
,field-value
)>
Make a deep copy of the Fields. Equivalent in behavior to calling the
fields
constructor on the return value of entries
. The resulting
fields
is mutable.
self
: borrow<fields
>
- own<
fields
>
Returns the method of the incoming request.
self
: borrow<incoming-request
>
Returns the path with query parameters from the request, as a string.
self
: borrow<incoming-request
>
Returns the protocol scheme from the request.
self
: borrow<incoming-request
>
- option<
scheme
>
Returns the authority of the Request's target URI, if present.
self
: borrow<incoming-request
>
Get the headers
associated with the request.
The returned headers
resource is immutable: set
, append
, and
delete
operations will fail with header-error.immutable
.
The headers
returned are a child resource: it must be dropped before
the parent incoming-request
is dropped. Dropping this
incoming-request
before all children are dropped will trap.
self
: borrow<incoming-request
>
- own<
headers
>
Gives the incoming-body
associated with this request. Will only
return success at most once, and subsequent calls will return error.
self
: borrow<incoming-request
>
- result<own<
incoming-body
>>
Construct a new outgoing-request
with a default method
of GET
, and
none
values for path-with-query
, scheme
, and authority
.
headers
is the HTTP Headers for the Request.
It is possible to construct, or manipulate with the accessor functions
below, an outgoing-request
with an invalid combination of scheme
and authority
, or headers
which are not permitted to be sent.
It is the obligation of the outgoing-handler.handle
implementation
to reject invalid constructions of outgoing-request
.
- own<
outgoing-request
>
Returns the resource corresponding to the outgoing Body for this Request.
Returns success on the first call: the outgoing-body
resource for
this outgoing-request
can be retrieved at most once. Subsequent
calls will return error.
self
: borrow<outgoing-request
>
- result<own<
outgoing-body
>>
Get the Method for the Request.
self
: borrow<outgoing-request
>
Set the Method for the Request. Fails if the string present in a
method.other
argument is not a syntactically valid method.
self
: borrow<outgoing-request
>method
:method
Get the combination of the HTTP Path and Query for the Request.
When none
, this represents an empty Path and empty Query.
self
: borrow<outgoing-request
>
Set the combination of the HTTP Path and Query for the Request.
When none
, this represents an empty Path and empty Query. Fails is the
string given is not a syntactically valid path and query uri component.
self
: borrow<outgoing-request
>path-with-query
: option<string
>
Get the HTTP Related Scheme for the Request. When none
, the
implementation may choose an appropriate default scheme.
self
: borrow<outgoing-request
>
- option<
scheme
>
Set the HTTP Related Scheme for the Request. When none
, the
implementation may choose an appropriate default scheme. Fails if the
string given is not a syntactically valid uri scheme.
self
: borrow<outgoing-request
>scheme
: option<scheme
>
Get the authority of the Request's target URI. A value of none
may be used
with Related Schemes which do not require an authority. The HTTP and
HTTPS schemes always require an authority.
self
: borrow<outgoing-request
>
Set the authority of the Request's target URI. A value of none
may be used
with Related Schemes which do not require an authority. The HTTP and
HTTPS schemes always require an authority. Fails if the string given is
not a syntactically valid URI authority.
self
: borrow<outgoing-request
>authority
: option<string
>
Get the headers associated with the Request.
The returned headers
resource is immutable: set
, append
, and
delete
operations will fail with header-error.immutable
.
This headers resource is a child: it must be dropped before the parent
outgoing-request
is dropped, or its ownership is transferred to
another component by e.g. outgoing-handler.handle
.
self
: borrow<outgoing-request
>
- own<
headers
>
Construct a default request-options
value.
- own<
request-options
>
The timeout for the initial connect to the HTTP Server.
self
: borrow<request-options
>
- option<
duration
>
Set the timeout for the initial connect to the HTTP Server. An error return value indicates that this timeout is not supported.
self
: borrow<request-options
>duration
: option<duration
>
The timeout for receiving the first byte of the Response body.
self
: borrow<request-options
>
- option<
duration
>
Set the timeout for receiving the first byte of the Response body. An error return value indicates that this timeout is not supported.
self
: borrow<request-options
>duration
: option<duration
>
The timeout for receiving subsequent chunks of bytes in the Response body stream.
self
: borrow<request-options
>
- option<
duration
>
Set the timeout for receiving subsequent chunks of bytes in the Response body stream. An error return value indicates that this timeout is not supported.
self
: borrow<request-options
>duration
: option<duration
>
Set the value of the response-outparam
to either send a response,
or indicate an error.
This method consumes the response-outparam
to ensure that it is
called at most once. If it is never called, the implementation
will respond with an error.
The user may provide an error
to response
to allow the
implementation determine how to respond with an HTTP error response.
param
: own<response-outparam
>response
: result<own<outgoing-response
>,error-code
>
Returns the status code from the incoming response.
self
: borrow<incoming-response
>
Returns the headers from the incoming response.
The returned headers
resource is immutable: set
, append
, and
delete
operations will fail with header-error.immutable
.
This headers resource is a child: it must be dropped before the parent
incoming-response
is dropped.
self
: borrow<incoming-response
>
- own<
headers
>
Returns the incoming body. May be called at most once. Returns error if called additional times.
self
: borrow<incoming-response
>
- result<own<
incoming-body
>>
Returns the contents of the body, as a stream of bytes.
Returns success on first call: the stream representing the contents can be retrieved at most once. Subsequent calls will return error.
The returned input-stream
resource is a child: it must be dropped
before the parent incoming-body
is dropped, or consumed by
incoming-body.finish
.
This invariant ensures that the implementation can determine whether
the user is consuming the contents of the body, waiting on the
future-trailers
to be ready, or neither. This allows for network
backpressure is to be applied when the user is consuming the body,
and for that backpressure to not inhibit delivery of the trailers if
the user does not read the entire body.
self
: borrow<incoming-body
>
- result<own<
input-stream
>>
Takes ownership of incoming-body
, and returns a future-trailers
.
This function will trap if the input-stream
child is still alive.
this
: own<incoming-body
>
- own<
future-trailers
>
Returns a pollable which becomes ready when either the trailers have
been received, or an error has occurred. When this pollable is ready,
the get
method will return some
.
self
: borrow<future-trailers
>
- own<
pollable
>
Returns the contents of the trailers, or an error which occurred, once the future is ready.
The outer option
represents future readiness. Users can wait on this
option
to become some
using the subscribe
method.
The outer result
is used to retrieve the trailers or error at most
once. It will be success on the first call in which the outer option
is some
, and error on subsequent calls.
The inner result
represents that either the HTTP Request or Response
body, as well as any trailers, were received successfully, or that an
error occurred receiving them. The optional trailers
indicates whether
or not trailers were present in the body.
When some trailers
are returned by this method, the trailers
resource is immutable, and a child. Use of the set
, append
, or
delete
methods will return an error, and the resource must be
dropped before the parent future-trailers
is dropped.
self
: borrow<future-trailers
>
- option<result<result<option<own<
trailers
>>,error-code
>>>
Construct an outgoing-response
, with a default status-code
of 200
.
If a different status-code
is needed, it must be set via the
set-status-code
method.
headers
is the HTTP Headers for the Response.
- own<
outgoing-response
>
Get the HTTP Status Code for the Response.
self
: borrow<outgoing-response
>
Set the HTTP Status Code for the Response. Fails if the status-code given is not a valid http status code.
self
: borrow<outgoing-response
>status-code
:status-code
Get the headers associated with the Request.
The returned headers
resource is immutable: set
, append
, and
delete
operations will fail with header-error.immutable
.
This headers resource is a child: it must be dropped before the parent
outgoing-request
is dropped, or its ownership is transferred to
another component by e.g. outgoing-handler.handle
.
self
: borrow<outgoing-response
>
- own<
headers
>
Returns the resource corresponding to the outgoing Body for this Response.
Returns success on the first call: the outgoing-body
resource for
this outgoing-response
can be retrieved at most once. Subsequent
calls will return error.
self
: borrow<outgoing-response
>
- result<own<
outgoing-body
>>
Returns a stream for writing the body contents.
The returned output-stream
is a child resource: it must be dropped
before the parent outgoing-body
resource is dropped (or finished),
otherwise the outgoing-body
drop or finish
will trap.
Returns success on the first call: the output-stream
resource for
this outgoing-body
may be retrieved at most once. Subsequent calls
will return error.
self
: borrow<outgoing-body
>
- result<own<
output-stream
>>
Finalize an outgoing body, optionally providing trailers. This must be
called to signal that the response is complete. If the outgoing-body
is dropped without calling outgoing-body.finalize
, the implementation
should treat the body as corrupted.
Fails if the body's outgoing-request
or outgoing-response
was
constructed with a Content-Length header, and the contents written
to the body (via write
) does not match the value given in the
Content-Length.
this
: own<outgoing-body
>trailers
: option<own<trailers
>>
- result<_,
error-code
>
Returns a pollable which becomes ready when either the Response has
been received, or an error has occurred. When this pollable is ready,
the get
method will return some
.
self
: borrow<future-incoming-response
>
- own<
pollable
>
Returns the incoming HTTP Response, or an error, once one is ready.
The outer option
represents future readiness. Users can wait on this
option
to become some
using the subscribe
method.
The outer result
is used to retrieve the response or error at most
once. It will be success on the first call in which the outer option
is some
, and error on subsequent calls.
The inner result
represents that either the incoming HTTP Response
status and headers have received successfully, or that an error
occurred. Errors may also occur while consuming the response body,
but those will be reported by the incoming-body
and its
output-stream
child.
self
: borrow<future-incoming-response
>
- option<result<result<own<
incoming-response
>,error-code
>>>
Import interface wasi:http/[email protected]
This interface defines a handler of outgoing HTTP Requests. It should be imported by components which wish to make HTTP Requests.
#### `type request-options` [`request-options`](#request_options)
#### `type future-incoming-response` [`future-incoming-response`](#future_incoming_response)
#### `type error-code` [`error-code`](#error_code)
----
This function is invoked with an outgoing HTTP Request, and it returns
a resource future-incoming-response
which represents an HTTP Response
which may arrive in the future.
The options
argument accepts optional parameters for the HTTP
protocol's transport layer.
This function may return an error if the outgoing-request
is invalid
or not allowed to be made. Otherwise, protocol errors are reported
through the future-incoming-response
.
request
: own<outgoing-request
>options
: option<own<request-options
>>
- result<own<
future-incoming-response
>,error-code
>
Export interface wasi:messaging/[email protected]
#### `type guest-configuration` [`guest-configuration`](#guest_configuration)
#### `type error` [`error`](#error)
----
Returns the list of channels (and extension metadata within guest-configuration) that this component should subscribe to and be handled by the subsequent handler within guest-configuration
- result<
guest-configuration
, own<error
>>
Whenever this guest receives a message in one of the subscribed channels, the message is sent to this handler
ms
: list<message
>
- result<_, own<
error
>>