wasi:cli/environment@0.2.8wasi:cli/exit@0.2.8wasi:io/error@0.2.8wasi:io/poll@0.2.8wasi:io/streams@0.2.8wasi:cli/stdin@0.2.8wasi:cli/stdout@0.2.8wasi:cli/stderr@0.2.8wasi:cli/terminal-input@0.2.8wasi:cli/terminal-output@0.2.8wasi:cli/terminal-stdin@0.2.8wasi:cli/terminal-stdout@0.2.8wasi:cli/terminal-stderr@0.2.8wasi:clocks/monotonic-clock@0.2.8wasi:clocks/wall-clock@0.2.8wasi:clocks/timezone@0.2.8wasi:filesystem/types@0.2.8wasi:filesystem/preopens@0.2.8wasi:sockets/network@0.2.8wasi:sockets/instance-network@0.2.8wasi:sockets/udp@0.2.8wasi:sockets/udp-create-socket@0.2.8wasi:sockets/tcp@0.2.8wasi:sockets/tcp-create-socket@0.2.8wasi:sockets/ip-name-lookup@0.2.8wasi:random/random@0.2.8wasi:random/insecure@0.2.8wasi:random/insecure-seed@0.2.8get-environment: funcGet the POSIX-style environment variables.
Each environment variable is provided as a pair of string variable names and string value.
Morally, these are a value import, but until value imports are available in the component model, this import function should return the same values each time it is called.
get-arguments: funcGet the POSIX-style arguments to the program.
initial-cwd: funcReturn a path that programs should use as their initial current working
directory, interpreting . as shorthand for this.
exit: funcExit the current instance and any linked instances.
exit-with-code: funcExit the current instance and any linked instances, reporting the specified status code to the host.
The meaning of the code depends on the context, with 0 usually meaning "success", and other values indicating various types of failure.
This function does not return; the effect is analogous to a trap, but without the connotation that something bad has happened.
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
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>.
error into a more
concrete type is open.[method]error.to-debug-string: funcReturns 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>A poll API intended to let users wait for I/O events on multiple handles 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.
Returns true when the pollable is ready, and false otherwise.
self: borrow<pollable>[method]pollable.block: funcblock 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: funcPoll 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:
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>>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 error
type pollable
variant stream-errorAn 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.
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.
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.[method]input-stream.read: funcPerform 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: u64u8>, stream-error>[method]input-stream.blocking-read: funcRead 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: u64u8>, stream-error>[method]input-stream.skip: funcSkip 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: u64u64, stream-error>[method]input-stream.blocking-skip: funcSkip 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: u64u64, stream-error>[method]input-stream.subscribe: funcCreate 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 pollables created with this function are dropped.
self: borrow<input-stream>pollable>[method]output-stream.check-write: funcCheck 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>u64, stream-error>[method]output-stream.write: funcPerform 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>stream-error>[method]output-stream.blocking-write-and-flush: funcPerform a write of up to 4096 bytes, and then flush the stream. Block until all of these operations are complete, or an error occurs.
Returns success when all of the contents written are successfully flushed to output. If an error occurs at any point before all contents are successfully flushed, that error is returned as soon as possible. If writing and flushing the complete contents causes the stream to become closed, this call should return success, and subsequent calls to check-write or other interfaces should return stream-error::closed.
self: borrow<output-stream>contents: list<u8>stream-error>[method]output-stream.flush: funcRequest 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>stream-error>[method]output-stream.blocking-flush: funcRequest to flush buffered output, and block until flush completes and stream is ready for writing again.
self: borrow<output-stream>stream-error>[method]output-stream.subscribe: funcCreate 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 pollables created with this function are dropped.
self: borrow<output-stream>pollable>[method]output-stream.write-zeroes: funcWrite 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: u64stream-error>[method]output-stream.blocking-write-zeroes-and-flush: funcPerform a write of up to 4096 zeroes, and then flush the stream. Block until all of these operations are complete, or an error occurs.
Functionality is equivelant to blocking-write-and-flush with
contents given as a list of len containing only zeroes.
self: borrow<output-stream>len: u64stream-error>[method]output-stream.splice: funcRead from one stream and write to another.
The behavior of splice is equivalent to:
check-write on the output-streamread on the input-stream with the smaller of the
check-write permitted length and the len provided to splicewrite on the output-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: u64u64, stream-error>[method]output-stream.blocking-splice: funcRead 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: u64u64, stream-error>type input-stream
get-stdin: funcinput-stream>type output-stream
get-stdout: funcoutput-stream>type output-stream
get-stderr: funcoutput-stream>Terminal input.
In the future, this may include functions for disabling echoing, disabling input buffering so that keyboard events are sent through immediately, querying supported features, and so on.
resource terminal-inputThe input side of a terminal.
Terminal output.
In the future, this may include functions for querying the terminal size, being notified of terminal size changes, querying supported features, and so on.
resource terminal-outputThe output side of a terminal.
An interface providing an optional terminal-input for stdin as a
link-time authority.
type terminal-input
get-terminal-stdin: funcIf stdin is connected to a terminal, return a terminal-input handle
allowing further interaction with it.
terminal-input>>An interface providing an optional terminal-output for stdout as a
link-time authority.
type terminal-output
get-terminal-stdout: funcIf stdout is connected to a terminal, return a terminal-output handle
allowing further interaction with it.
terminal-output>>An interface providing an optional terminal-output for stderr as a
link-time authority.
type terminal-output
get-terminal-stderr: funcIf stderr is connected to a terminal, return a terminal-output handle
allowing further interaction with it.
terminal-output>>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.
type pollable
type instantu64
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.
type durationu64
A duration of time, in nanoseconds.
now: funcRead the current value of the clock.
The clock is monotonic, therefore calling this function repeatedly will produce a sequence of non-decreasing values.
For completeness, this function traps if it's not possible to represent
the value of the clock in an instant. Consequently, implementations
should ensure that the starting time is low enough to avoid the
possibility of overflow in practice.
resolution: funcQuery the resolution of the clock. Returns the duration of time corresponding to a clock tick.
subscribe-instant: funcCreate a pollable which will resolve once the specified instant
has occurred.
when: instantpollable>subscribe-duration: funcCreate a pollable that will resolve after the specified duration has
elapsed from the time this function is invoked.
when: durationpollable>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.
record datetimeA time and date in seconds plus nanoseconds.
now: funcRead 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.
resolution: funcQuery the resolution of the clock.
The nanoseconds field of the output is always less than 1000000000.
type datetime
record timezone-displayInformation useful for displaying the timezone of a specific datetime.
This information may vary within a single timezone to reflect daylight
saving time adjustments.
utc-offset: s32
The number of seconds difference between UTC time and the local time of the timezone.
The returned value will always be less than 86400 which is the number of seconds in a day (246060).
In implementations that do not expose an actual time zone, this should return 0.
The abbreviated name of the timezone to display to a user. The name `UTC` indicates Coordinated Universal Time. Otherwise, this should reference local standards for the name of the time zone.
In implementations that do not expose an actual time zone, this
should be the string UTC.
In time zones that do not have an applicable name, a formatted
representation of the UTC offset may be returned, such as -04:00.
Whether daylight saving time is active.
In implementations that do not expose an actual time zone, this should return false.
display: funcReturn information needed to display the given datetime. This includes
the UTC offset, the time zone name, and a flag indicating whether
daylight saving time is active.
If the timezone cannot be determined for the given datetime, return a
timezone-display for UTC with a utc-offset of 0 and no daylight
saving time.
when: datetimeutc-offset: funcThe same as display, but only return the UTC offset.
when: datetimeWASI filesystem is a filesystem API primarily intended to let users run WASI programs that access their files on their existing filesystems, without significant overhead.
It is intended to be roughly portable between Unix-family platforms and Windows, though it does not hide many of the major differences.
Paths are passed as interface-type strings, meaning they must consist of
a sequence of Unicode Scalar Values (USVs). Some filesystems may contain
paths which are not accessible by this API.
The directory separator in WASI is always the forward-slash (/).
All paths in WASI are relative paths, and are interpreted relative to a
descriptor referring to a base directory. If a path argument to any WASI
function starts with /, or if any step of resolving a path, including
.. and symbolic link steps, reaches a directory outside of the base
directory, or reaches a symlink to an absolute or rooted path in the
underlying filesystem, the function fails with error-code::not-permitted.
For more information about WASI path resolution and sandboxing, see WASI filesystem path resolution.
type input-stream
type output-stream
type error
type datetime
type filesizeu64
File size or length of a region within a file.
enum descriptor-typeThe type of a filesystem object referenced by a descriptor.
Note: This was called filetype in earlier versions of WASI.
The type of the descriptor or file is unknown or is different from any of the other types specified.
The descriptor refers to a block device inode.
The descriptor refers to a character device inode.
The descriptor refers to a directory inode.
The descriptor refers to a named pipe.
The file refers to a symbolic link inode.
The descriptor refers to a regular file inode.
The descriptor refers to a socket.
flags descriptor-flagsDescriptor flags.
Note: This was called fdflags in earlier versions of WASI.
Read mode: Data can be read.
Write mode: Data can be written to.
Request that writes be performed according to synchronized I/O file integrity completion. The data stored in the file and the file's metadata are synchronized. This is similar to `O_SYNC` in POSIX.
The precise semantics of this operation have not yet been defined for WASI. At this time, it should be interpreted as a request, and not a requirement.
Request that writes be performed according to synchronized I/O data integrity completion. Only the data stored in the file is synchronized. This is similar to `O_DSYNC` in POSIX.
The precise semantics of this operation have not yet been defined for WASI. At this time, it should be interpreted as a request, and not a requirement.
Requests that reads be performed at the same level of integrity requested for writes. This is similar to `O_RSYNC` in POSIX.
The precise semantics of this operation have not yet been defined for WASI. At this time, it should be interpreted as a request, and not a requirement.
Mutating directories mode: Directory contents may be mutated.
When this flag is unset on a descriptor, operations using the
descriptor which would create, rename, delete, modify the data or
metadata of filesystem objects, or obtain another handle which
would permit any of those, shall fail with error-code::read-only if
they would otherwise succeed.
This may only be set on directories.
flags path-flagsFlags determining the method of how paths are resolved.
flags open-flagsOpen flags used by open-at.
Create file if it does not exist, similar to `O_CREAT` in POSIX.
Fail if not a directory, similar to `O_DIRECTORY` in POSIX.
Fail if file already exists, similar to `O_EXCL` in POSIX.
Truncate file to size 0, similar to `O_TRUNC` in POSIX.
type link-countu64
Number of hard links to an inode.
record descriptor-statFile attributes.
Note: This was called filestat in earlier versions of WASI.
type: descriptor-type
File type.
Number of hard links to the file.
size: filesize
For regular files, the file size in bytes. For symbolic links, the length in bytes of the pathname contained in the symbolic link.
data-access-timestamp: option<datetime>
Last data access timestamp.
If the option is none, the platform doesn't maintain an access
timestamp for this file.
data-modification-timestamp: option<datetime>
Last data modification timestamp.
If the option is none, the platform doesn't maintain a
modification timestamp for this file.
status-change-timestamp: option<datetime>
Last file status-change timestamp.
If the option is none, the platform doesn't maintain a
status-change timestamp for this file.
variant new-timestampWhen setting a timestamp, this gives the value to set it to.
Leave the timestamp set to its previous value.
Set the timestamp to the current time of the system clock associated with the filesystem.
timestamp: datetime
Set the timestamp to the given value.
record directory-entryA directory entry.
type: descriptor-type
The type of the file referred to by this directory entry.
The name of the object.
enum error-codeError codes returned by functions, similar to errno in POSIX.
Not all of these error codes are returned by the functions provided by this
API; some are used in higher-level library layers, and others are provided
merely for alignment with POSIX.
Permission denied, similar to `EACCES` in POSIX.
Resource unavailable, or operation would block, similar to `EAGAIN` and `EWOULDBLOCK` in POSIX.
Connection already in progress, similar to `EALREADY` in POSIX.
Bad descriptor, similar to `EBADF` in POSIX.
Device or resource busy, similar to `EBUSY` in POSIX.
Resource deadlock would occur, similar to `EDEADLK` in POSIX.
Storage quota exceeded, similar to `EDQUOT` in POSIX.
File exists, similar to `EEXIST` in POSIX.
File too large, similar to `EFBIG` in POSIX.
Illegal byte sequence, similar to `EILSEQ` in POSIX.
Operation in progress, similar to `EINPROGRESS` in POSIX.
Interrupted function, similar to `EINTR` in POSIX.
Invalid argument, similar to `EINVAL` in POSIX.
I/O error, similar to `EIO` in POSIX.
Is a directory, similar to `EISDIR` in POSIX.
Too many levels of symbolic links, similar to `ELOOP` in POSIX.
Too many links, similar to `EMLINK` in POSIX.
Message too large, similar to `EMSGSIZE` in POSIX.
Filename too long, similar to `ENAMETOOLONG` in POSIX.
No such device, similar to `ENODEV` in POSIX.
No such file or directory, similar to `ENOENT` in POSIX.
No locks available, similar to `ENOLCK` in POSIX.
Not enough space, similar to `ENOMEM` in POSIX.
No space left on device, similar to `ENOSPC` in POSIX.
Not a directory or a symbolic link to a directory, similar to `ENOTDIR` in POSIX.
Directory not empty, similar to `ENOTEMPTY` in POSIX.
State not recoverable, similar to `ENOTRECOVERABLE` in POSIX.
Not supported, similar to `ENOTSUP` and `ENOSYS` in POSIX.
Inappropriate I/O control operation, similar to `ENOTTY` in POSIX.
No such device or address, similar to `ENXIO` in POSIX.
Value too large to be stored in data type, similar to `EOVERFLOW` in POSIX.
Operation not permitted, similar to `EPERM` in POSIX.
Broken pipe, similar to `EPIPE` in POSIX.
Read-only file system, similar to `EROFS` in POSIX.
Invalid seek, similar to `ESPIPE` in POSIX.
Text file busy, similar to `ETXTBSY` in POSIX.
Cross-device link, similar to `EXDEV` in POSIX.
enum adviceFile or memory access pattern advisory information.
The application has no advice to give on its behavior with respect to the specified data.
The application expects to access the specified data sequentially from lower offsets to higher offsets.
The application expects to access the specified data in a random order.
The application expects to access the specified data in the near future.
The application expects that it will not access the specified data in the near future.
The application expects to access the specified data once and then not reuse it thereafter.
record metadata-hash-valueA 128-bit hash value, split into parts because wasm doesn't have a 128-bit integer type.
resource descriptorA descriptor is a reference to a filesystem object, which may be a file, directory, named pipe, special file, or other object on which filesystem calls may be made.
resource directory-entry-stream[method]descriptor.read-via-stream: funcReturn a stream for reading from a file, if available.
May fail with an error-code describing why the file cannot be read.
Multiple read, write, and append streams may be active on the same open file and they do not interfere with each other.
Note: This allows using read-stream, which is similar to read in POSIX.
self: borrow<descriptor>offset: filesizeinput-stream>, error-code>[method]descriptor.write-via-stream: funcReturn a stream for writing to a file, if available.
May fail with an error-code describing why the file cannot be written.
Note: This allows using write-stream, which is similar to write in
POSIX.
self: borrow<descriptor>offset: filesizeoutput-stream>, error-code>[method]descriptor.append-via-stream: funcReturn a stream for appending to a file, if available.
May fail with an error-code describing why the file cannot be appended.
Note: This allows using write-stream, which is similar to write with
O_APPEND in POSIX.
self: borrow<descriptor>output-stream>, error-code>[method]descriptor.advise: funcProvide file advisory information on a descriptor.
This is similar to posix_fadvise in POSIX.
self: borrow<descriptor>offset: filesizelength: filesizeadvice: adviceerror-code>[method]descriptor.sync-data: funcSynchronize the data of a file to disk.
This function succeeds with no effect if the file descriptor is not opened for writing.
Note: This is similar to fdatasync in POSIX.
self: borrow<descriptor>error-code>[method]descriptor.get-flags: funcGet flags associated with a descriptor.
Note: This returns similar flags to fcntl(fd, F_GETFL) in POSIX.
Note: This returns the value that was the fs_flags value returned
from fdstat_get in earlier versions of WASI.
self: borrow<descriptor>descriptor-flags, error-code>[method]descriptor.get-type: funcGet the dynamic type of a descriptor.
Note: This returns the same value as the type field of the fd-stat
returned by stat, stat-at and similar.
Note: This returns similar flags to the st_mode & S_IFMT value provided
by fstat in POSIX.
Note: This returns the value that was the fs_filetype value returned
from fdstat_get in earlier versions of WASI.
self: borrow<descriptor>descriptor-type, error-code>[method]descriptor.set-size: funcAdjust the size of an open file. If this increases the file's size, the extra bytes are filled with zeros.
Note: This was called fd_filestat_set_size in earlier versions of WASI.
self: borrow<descriptor>size: filesizeerror-code>[method]descriptor.set-times: funcAdjust the timestamps of an open file or directory.
Note: This is similar to futimens in POSIX.
Note: This was called fd_filestat_set_times in earlier versions of WASI.
self: borrow<descriptor>data-access-timestamp: new-timestampdata-modification-timestamp: new-timestamperror-code>[method]descriptor.read: funcRead from a descriptor, without using and updating the descriptor's offset.
This function returns a list of bytes containing the data that was
read, along with a bool which, when true, indicates that the end of the
file was reached. The returned list will contain up to length bytes; it
may return fewer than requested, if the end of the file is reached or
if the I/O operation is interrupted.
In the future, this may change to return a stream<u8, error-code>.
Note: This is similar to pread in POSIX.
self: borrow<descriptor>length: filesizeoffset: filesizeu8>, bool), error-code>[method]descriptor.write: funcWrite to a descriptor, without using and updating the descriptor's offset.
It is valid to write past the end of a file; the file is extended to the extent of the write, with bytes between the previous end and the start of the write set to zero.
In the future, this may change to take a stream<u8, error-code>.
Note: This is similar to pwrite in POSIX.
self: borrow<descriptor>buffer: list<u8>offset: filesizefilesize, error-code>[method]descriptor.read-directory: funcRead directory entries from a directory.
On filesystems where directories contain entries referring to themselves
and their parents, often named . and .. respectively, these entries
are omitted.
This always returns a new stream which starts at the beginning of the directory. Multiple streams may be active on the same directory, and they do not interfere with each other.
self: borrow<descriptor>directory-entry-stream>, error-code>[method]descriptor.sync: funcSynchronize the data and metadata of a file to disk.
This function succeeds with no effect if the file descriptor is not opened for writing.
Note: This is similar to fsync in POSIX.
self: borrow<descriptor>error-code>[method]descriptor.create-directory-at: funcCreate a directory.
Note: This is similar to mkdirat in POSIX.
self: borrow<descriptor>path: stringerror-code>[method]descriptor.stat: funcReturn the attributes of an open file or directory.
Note: This is similar to fstat in POSIX, except that it does not return
device and inode information. For testing whether two descriptors refer to
the same underlying filesystem object, use is-same-object. To obtain
additional data that can be used do determine whether a file has been
modified, use metadata-hash.
Note: This was called fd_filestat_get in earlier versions of WASI.
self: borrow<descriptor>descriptor-stat, error-code>[method]descriptor.stat-at: funcReturn the attributes of a file or directory.
Note: This is similar to fstatat in POSIX, except that it does not
return device and inode information. See the stat description for a
discussion of alternatives.
Note: This was called path_filestat_get in earlier versions of WASI.
self: borrow<descriptor>path-flags: path-flagspath: stringdescriptor-stat, error-code>[method]descriptor.set-times-at: funcAdjust the timestamps of a file or directory.
Note: This is similar to utimensat in POSIX.
Note: This was called path_filestat_set_times in earlier versions of
WASI.
self: borrow<descriptor>path-flags: path-flagspath: stringdata-access-timestamp: new-timestampdata-modification-timestamp: new-timestamperror-code>[method]descriptor.link-at: funcCreate a hard link.
Fails with error-code::no-entry if the old path does not exist,
with error-code::exist if the new path already exists, and
error-code::not-permitted if the old path is not a file.
Note: This is similar to linkat in POSIX.
self: borrow<descriptor>old-path-flags: path-flagsold-path: stringnew-descriptor: borrow<descriptor>new-path: stringerror-code>[method]descriptor.open-at: funcOpen a file or directory.
If flags contains descriptor-flags::mutate-directory, and the base
descriptor doesn't have descriptor-flags::mutate-directory set,
open-at fails with error-code::read-only.
If flags contains write or mutate-directory, or open-flags
contains truncate or create, and the base descriptor doesn't have
descriptor-flags::mutate-directory set, open-at fails with
error-code::read-only.
Note: This is similar to openat in POSIX.
self: borrow<descriptor>path-flags: path-flagspath: stringopen-flags: open-flagsflags: descriptor-flagsdescriptor>, error-code>[method]descriptor.readlink-at: funcRead the contents of a symbolic link.
If the contents contain an absolute or rooted path in the underlying
filesystem, this function fails with error-code::not-permitted.
Note: This is similar to readlinkat in POSIX.
self: borrow<descriptor>path: stringstring, error-code>[method]descriptor.remove-directory-at: funcRemove a directory.
Return error-code::not-empty if the directory is not empty.
Note: This is similar to unlinkat(fd, path, AT_REMOVEDIR) in POSIX.
self: borrow<descriptor>path: stringerror-code>[method]descriptor.rename-at: funcRename a filesystem object.
Note: This is similar to renameat in POSIX.
self: borrow<descriptor>old-path: stringnew-descriptor: borrow<descriptor>new-path: stringerror-code>[method]descriptor.symlink-at: funcCreate a symbolic link (also known as a "symlink").
If old-path starts with /, the function fails with
error-code::not-permitted.
Note: This is similar to symlinkat in POSIX.
self: borrow<descriptor>old-path: stringnew-path: stringerror-code>[method]descriptor.unlink-file-at: funcUnlink a filesystem object that is not a directory.
Return error-code::is-directory if the path refers to a directory.
Note: This is similar to unlinkat(fd, path, 0) in POSIX.
self: borrow<descriptor>path: stringerror-code>[method]descriptor.is-same-object: funcTest whether two descriptors refer to the same filesystem object.
In POSIX, this corresponds to testing whether the two descriptors have the
same device (st_dev) and inode (st_ino or d_ino) numbers.
wasi-filesystem does not expose device and inode numbers, so this function
may be used instead.
self: borrow<descriptor>other: borrow<descriptor>[method]descriptor.metadata-hash: funcReturn a hash of the metadata associated with a filesystem object referred to by a descriptor.
This returns a hash of the last-modification timestamp and file size, and may also include the inode number, device number, birth timestamp, and other metadata fields that may change when the file is modified or replaced. It may also include a secret value chosen by the implementation and not otherwise exposed.
Implementations are encouraged to provide the following properties:
However, none of these is required.
self: borrow<descriptor>metadata-hash-value, error-code>[method]descriptor.metadata-hash-at: funcReturn a hash of the metadata associated with a filesystem object referred to by a directory descriptor and a relative path.
This performs the same hash computation as metadata-hash.
self: borrow<descriptor>path-flags: path-flagspath: stringmetadata-hash-value, error-code>[method]directory-entry-stream.read-directory-entry: funcRead a single directory entry from a directory-entry-stream.
self: borrow<directory-entry-stream>directory-entry>, error-code>filesystem-error-code: funcAttempts to extract a filesystem-related error-code from the stream
error provided.
Stream operations which return stream-error::last-operation-failed
have a payload with more information about the operation that failed.
This payload can be passed through to this function to see if there's
filesystem-related information about the error to return.
Note that this function is fallible because not all stream-related errors are filesystem-related errors.
err: borrow<error>error-code>type descriptor
get-directories: funcReturn the set of preopened directories, and their paths.
descriptor>, string)>type error
resource networkAn opaque resource that represents access to (a subset of) the network. This enables context-based security for networking. There is no need for this to map 1:1 to a physical network interface.
enum error-codeError codes.
In theory, every API can return any error code. In practice, API's typically only return the errors documented per API combined with a couple of errors that are always possible:
unknownaccess-deniednot-supportedout-of-memoryconcurrency-conflictSee each individual API for what the POSIX equivalents are. They sometimes differ per API.
Unknown error
Access denied.
POSIX equivalent: EACCES, EPERM
The operation is not supported.
POSIX equivalent: EOPNOTSUPP
One of the arguments is invalid.
POSIX equivalent: EINVAL
Not enough memory to complete the operation.
POSIX equivalent: ENOMEM, ENOBUFS, EAI_MEMORY
The operation timed out before it could finish completely.
This operation is incompatible with another asynchronous operation that is already in progress.
POSIX equivalent: EALREADY
Trying to finish an asynchronous operation that: - has not been started yet, or: - was already finished by a previous `finish-*` call.
Note: this is scheduled to be removed when futures are natively supported.
The operation has been aborted because it could not be completed immediately.
Note: this is scheduled to be removed when futures are natively supported.
The operation is not valid in the socket's current state.
A new socket resource could not be created because of a system limit.
A bind operation failed because the provided address is not an address that the `network` can bind to.
A bind operation failed because the provided address is already in use or because there are no ephemeral ports available.
The remote address is not reachable
The TCP connection was forcefully rejected
The TCP connection was reset.
A TCP connection was aborted.
The size of a datagram sent to a UDP socket exceeded the maximum supported size.
Name does not exist or has no suitable associated IP addresses.
A temporary failure in name resolution occurred.
A permanent failure in name resolution occurred.
enum ip-address-familytuple ipv4-addresstuple ipv6-addressvariant ip-addressipv4: ipv4-addressipv6: ipv6-addressrecord ipv4-socket-addresssin_port
address: ipv4-address
sin_addr
record ipv6-socket-addresssin6_port
sin6_flowinfo
address: ipv6-address
sin6_addr
sin6_scope_id
variant ip-socket-addressipv4: ipv4-socket-addressipv6: ipv6-socket-addressnetwork-error-code: funcAttempts to extract a network-related error-code from the stream
error provided.
Stream operations which return stream-error::last-operation-failed
have a payload with more information about the operation that failed.
This payload can be passed through to this function to see if there's
network-related information about the error to return.
Note that this function is fallible because not all stream-related errors are network-related errors.
err: borrow<error>error-code>This interface provides a value-export of the default network handle..
type network
instance-network: funcGet a handle to the default network.
network>type pollable
type network
type error-code
type ip-socket-address
type ip-address-family
record incoming-datagramA received datagram.
The payload.
Theoretical max size: ~64 KiB. In practice, typically less than 1500 bytes.
remote-address: ip-socket-address
The source address.
This field is guaranteed to match the remote address the stream was initialized with, if any.
Equivalent to the src_addr out parameter of recvfrom.
record outgoing-datagramA datagram to be sent out.
The payload.
remote-address: option<ip-socket-address>
The destination address.
The requirements on this field depend on how the stream was initialized:
If this value is None, the send operation is equivalent to send in POSIX. Otherwise it is equivalent to sendto.
resource udp-socketA UDP socket handle.
resource incoming-datagram-streamresource outgoing-datagram-stream[method]udp-socket.start-bind: funcBind the socket to a specific network on the provided IP address and port.
If the IP address is zero (0.0.0.0 in IPv4, :: in IPv6), it is left to the implementation to decide which
network interface(s) to bind to.
If the port is zero, the socket will be bound to a random free port.
invalid-argument: The local-address has the wrong address family. (EAFNOSUPPORT, EFAULT on Windows)invalid-state: The socket is already bound. (EINVAL)address-in-use: No ephemeral ports available. (EADDRINUSE, ENOBUFS on Windows)address-in-use: Address is already in use. (EADDRINUSE)address-not-bindable: local-address is not an address that the network can bind to. (EADDRNOTAVAIL)not-in-progress: A bind operation is not in progress.would-block: Can't finish the operation, it is still in progress. (EWOULDBLOCK, EAGAIN)Unlike in POSIX, in WASI the bind operation is async. This enables
interactive WASI hosts to inject permission prompts. Runtimes that
don't want to make use of this ability can simply call the native
bind as part of either start-bind or finish-bind.
self: borrow<udp-socket>network: borrow<network>local-address: ip-socket-addresserror-code>[method]udp-socket.finish-bind: funcself: borrow<udp-socket>error-code>[method]udp-socket.stream: funcSet up inbound & outbound communication channels, optionally to a specific peer.
This function only changes the local socket configuration and does not generate any network traffic.
On success, the remote-address of the socket is updated. The local-address may be updated as well,
based on the best network path to remote-address.
When a remote-address is provided, the returned streams are limited to communicating with that specific peer:
send can only be used to send to this destination.receive will only return datagrams sent from the provided remote-address.This method may be called multiple times on the same socket to change its association, but
only the most recently returned pair of streams will be operational. Implementations may trap if
the streams returned by a previous invocation haven't been dropped yet before calling stream again.
The POSIX equivalent in pseudo-code is:
if (was previously connected) {
connect(s, AF_UNSPEC)
}
if (remote_address is Some) {
connect(s, remote_address)
}
Unlike in POSIX, the socket must already be explicitly bound.
invalid-argument: The remote-address has the wrong address family. (EAFNOSUPPORT)invalid-argument: The IP address in remote-address is set to INADDR_ANY (0.0.0.0 / ::). (EDESTADDRREQ, EADDRNOTAVAIL)invalid-argument: The port in remote-address is set to 0. (EDESTADDRREQ, EADDRNOTAVAIL)invalid-state: The socket is not bound.address-in-use: Tried to perform an implicit bind, but there were no ephemeral ports available. (EADDRINUSE, EADDRNOTAVAIL on Linux, EAGAIN on BSD)remote-unreachable: The remote address is not reachable. (ECONNRESET, ENETRESET, EHOSTUNREACH, EHOSTDOWN, ENETUNREACH, ENETDOWN, ENONET)connection-refused: The connection was refused. (ECONNREFUSED)self: borrow<udp-socket>remote-address: option<ip-socket-address>incoming-datagram-stream>, own<outgoing-datagram-stream>), error-code>[method]udp-socket.local-address: funcGet the current bound address.
POSIX mentions:
If the socket has not been bound to a local name, the value stored in the object pointed to by
addressis unspecified.
WASI is stricter and requires local-address to return invalid-state when the socket hasn't been bound yet.
invalid-state: The socket is not bound to any local address.self: borrow<udp-socket>ip-socket-address, error-code>[method]udp-socket.remote-address: funcGet the address the socket is currently streaming to.
invalid-state: The socket is not streaming to a specific remote address. (ENOTCONN)self: borrow<udp-socket>ip-socket-address, error-code>[method]udp-socket.address-family: funcWhether this is a IPv4 or IPv6 socket.
Equivalent to the SO_DOMAIN socket option.
self: borrow<udp-socket>[method]udp-socket.unicast-hop-limit: funcEquivalent to the IP_TTL & IPV6_UNICAST_HOPS socket options.
If the provided value is 0, an invalid-argument error is returned.
invalid-argument: (set) The TTL value must be 1 or higher.self: borrow<udp-socket>u8, error-code>[method]udp-socket.set-unicast-hop-limit: funcself: borrow<udp-socket>value: u8error-code>[method]udp-socket.receive-buffer-size: funcThe kernel buffer space reserved for sends/receives on this socket.
If the provided value is 0, an invalid-argument error is returned.
Any other value will never cause an error, but it might be silently clamped and/or rounded.
I.e. after setting a value, reading the same setting back may return a different value.
Equivalent to the SO_RCVBUF and SO_SNDBUF socket options.
invalid-argument: (set) The provided value was 0.self: borrow<udp-socket>u64, error-code>[method]udp-socket.set-receive-buffer-size: funcself: borrow<udp-socket>value: u64error-code>[method]udp-socket.send-buffer-size: funcself: borrow<udp-socket>u64, error-code>[method]udp-socket.set-send-buffer-size: funcself: borrow<udp-socket>value: u64error-code>[method]udp-socket.subscribe: funcCreate a pollable which will resolve once the socket is ready for I/O.
Note: this function is here for WASI 0.2 only.
It's planned to be removed when future is natively supported in Preview3.
self: borrow<udp-socket>pollable>[method]incoming-datagram-stream.receive: funcReceive messages on the socket.
This function attempts to receive up to max-results datagrams on the socket without blocking.
The returned list may contain fewer elements than requested, but never more.
This function returns successfully with an empty list when either:
max-results is 0, or:max-results is greater than 0, but no results are immediately available.
This function never returns error(would-block).remote-unreachable: The remote address is not reachable. (ECONNRESET, ENETRESET on Windows, EHOSTUNREACH, EHOSTDOWN, ENETUNREACH, ENETDOWN, ENONET)connection-refused: The connection was refused. (ECONNREFUSED)self: borrow<incoming-datagram-stream>max-results: u64incoming-datagram>, error-code>[method]incoming-datagram-stream.subscribe: funcCreate a pollable which will resolve once the stream is ready to receive again.
Note: this function is here for WASI 0.2 only.
It's planned to be removed when future is natively supported in Preview3.
self: borrow<incoming-datagram-stream>pollable>[method]outgoing-datagram-stream.check-send: funcCheck readiness for sending. This function never blocks.
Returns the number of datagrams permitted for the next call to send,
or an error. Calling send with more datagrams than this function has
permitted will trap.
When this function returns ok(0), the subscribe pollable will
become ready when this function will report at least ok(1), or an
error.
Never returns would-block.
self: borrow<outgoing-datagram-stream>u64, error-code>[method]outgoing-datagram-stream.send: funcSend messages on the socket.
This function attempts to send all provided datagrams on the socket without blocking and
returns how many messages were actually sent (or queued for sending). This function never
returns error(would-block). If none of the datagrams were able to be sent, ok(0) is returned.
This function semantically behaves the same as iterating the datagrams list and sequentially
sending each individual datagram until either the end of the list has been reached or the first error occurred.
If at least one datagram has been sent successfully, this function never returns an error.
If the input list is empty, the function returns ok(0).
Each call to send must be permitted by a preceding check-send. Implementations must trap if
either check-send was not called or datagrams contains more items than check-send permitted.
invalid-argument: The remote-address has the wrong address family. (EAFNOSUPPORT)invalid-argument: The IP address in remote-address is set to INADDR_ANY (0.0.0.0 / ::). (EDESTADDRREQ, EADDRNOTAVAIL)invalid-argument: The port in remote-address is set to 0. (EDESTADDRREQ, EADDRNOTAVAIL)invalid-argument: The socket is in "connected" mode and remote-address is some value that does not match the address passed to stream. (EISCONN)invalid-argument: The socket is not "connected" and no value for remote-address was provided. (EDESTADDRREQ)remote-unreachable: The remote address is not reachable. (ECONNRESET, ENETRESET on Windows, EHOSTUNREACH, EHOSTDOWN, ENETUNREACH, ENETDOWN, ENONET)connection-refused: The connection was refused. (ECONNREFUSED)datagram-too-large: The datagram is too large. (EMSGSIZE)self: borrow<outgoing-datagram-stream>datagrams: list<outgoing-datagram>u64, error-code>[method]outgoing-datagram-stream.subscribe: funcCreate a pollable which will resolve once the stream is ready to send again.
Note: this function is here for WASI 0.2 only.
It's planned to be removed when future is natively supported in Preview3.
self: borrow<outgoing-datagram-stream>pollable>type network
type error-code
type ip-address-family
type udp-socket
create-udp-socket: funcCreate a new UDP socket.
Similar to socket(AF_INET or AF_INET6, SOCK_DGRAM, IPPROTO_UDP) in POSIX.
On IPv6 sockets, IPV6_V6ONLY is enabled by default and can't be configured otherwise.
This function does not require a network capability handle. This is considered to be safe because
at time of creation, the socket is not bound to any network yet. Up to the moment bind is called,
the socket is effectively an in-memory configuration object, unable to communicate with the outside world.
All sockets are non-blocking. Use the wasi-poll interface to block on asynchronous operations.
not-supported: The specified address-family is not supported. (EAFNOSUPPORT)new-socket-limit: The new socket resource could not be created because of a system limit. (EMFILE, ENFILE)address-family: ip-address-familyudp-socket>, error-code>type input-stream
type output-stream
type pollable
type duration
type network
type error-code
type ip-socket-address
type ip-address-family
enum shutdown-typeSimilar to `SHUT_RD` in POSIX.
Similar to `SHUT_WR` in POSIX.
Similar to `SHUT_RDWR` in POSIX.
resource tcp-socketA TCP socket resource.
The socket can be in one of the following states:
unboundbind-in-progressbound (See note below)listen-in-progresslisteningconnect-in-progressconnectedclosed
See https://github.com/WebAssembly/wasi-sockets/blob/main/TcpSocketOperationalSemantics.md
for more information.Note: Except where explicitly mentioned, whenever this documentation uses
the term "bound" without backticks it actually means: in the bound state or higher.
(i.e. bound, listen-in-progress, listening, connect-in-progress or connected)
network::error-code type, TCP socket methods may always return
error(invalid-state) when in the closed state.[method]tcp-socket.start-bind: funcBind the socket to a specific network on the provided IP address and port.
If the IP address is zero (0.0.0.0 in IPv4, :: in IPv6), it is left to the implementation to decide which
network interface(s) to bind to.
If the TCP/UDP port is zero, the socket will be bound to a random free port.
Bind can be attempted multiple times on the same socket, even with different arguments on each iteration. But never concurrently and only as long as the previous bind failed. Once a bind succeeds, the binding can't be changed anymore.
invalid-argument: The local-address has the wrong address family. (EAFNOSUPPORT, EFAULT on Windows)invalid-argument: local-address is not a unicast address. (EINVAL)invalid-argument: local-address is an IPv4-mapped IPv6 address. (EINVAL)invalid-state: The socket is already bound. (EINVAL)address-in-use: No ephemeral ports available. (EADDRINUSE, ENOBUFS on Windows)address-in-use: Address is already in use. (EADDRINUSE)address-not-bindable: local-address is not an address that the network can bind to. (EADDRNOTAVAIL)not-in-progress: A bind operation is not in progress.would-block: Can't finish the operation, it is still in progress. (EWOULDBLOCK, EAGAIN)When binding to a non-zero port, this bind operation shouldn't be affected by the TIME_WAIT state of a recently closed socket on the same local address. In practice this means that the SO_REUSEADDR socket option should be set implicitly on all platforms, except on Windows where this is the default behavior and SO_REUSEADDR performs something different entirely.
Unlike in POSIX, in WASI the bind operation is async. This enables
interactive WASI hosts to inject permission prompts. Runtimes that
don't want to make use of this ability can simply call the native
bind as part of either start-bind or finish-bind.
self: borrow<tcp-socket>network: borrow<network>local-address: ip-socket-addresserror-code>[method]tcp-socket.finish-bind: funcself: borrow<tcp-socket>error-code>[method]tcp-socket.start-connect: funcConnect to a remote endpoint.
On success:
connected state.After a failed connection attempt, the socket will be in the closed
state and the only valid action left is to drop the socket. A single
socket can not be used to connect more than once.
invalid-argument: The remote-address has the wrong address family. (EAFNOSUPPORT)invalid-argument: remote-address is not a unicast address. (EINVAL, ENETUNREACH on Linux, EAFNOSUPPORT on MacOS)invalid-argument: remote-address is an IPv4-mapped IPv6 address. (EINVAL, EADDRNOTAVAIL on Illumos)invalid-argument: The IP address in remote-address is set to INADDR_ANY (0.0.0.0 / ::). (EADDRNOTAVAIL on Windows)invalid-argument: The port in remote-address is set to 0. (EADDRNOTAVAIL on Windows)invalid-argument: The socket is already attached to a different network. The network passed to connect must be identical to the one passed to bind.invalid-state: The socket is already in the connected state. (EISCONN)invalid-state: The socket is already in the listening state. (EOPNOTSUPP, EINVAL on Windows)timeout: Connection timed out. (ETIMEDOUT)connection-refused: The connection was forcefully rejected. (ECONNREFUSED)connection-reset: The connection was reset. (ECONNRESET)connection-aborted: The connection was aborted. (ECONNABORTED)remote-unreachable: The remote address is not reachable. (EHOSTUNREACH, EHOSTDOWN, ENETUNREACH, ENETDOWN, ENONET)address-in-use: Tried to perform an implicit bind, but there were no ephemeral ports available. (EADDRINUSE, EADDRNOTAVAIL on Linux, EAGAIN on BSD)not-in-progress: A connect operation is not in progress.would-block: Can't finish the operation, it is still in progress. (EWOULDBLOCK, EAGAIN)The POSIX equivalent of start-connect is the regular connect syscall.
Because all WASI sockets are non-blocking this is expected to return
EINPROGRESS, which should be translated to ok() in WASI.
The POSIX equivalent of finish-connect is a poll for event POLLOUT
with a timeout of 0 on the socket descriptor. Followed by a check for
the SO_ERROR socket option, in case the poll signaled readiness.
self: borrow<tcp-socket>network: borrow<network>remote-address: ip-socket-addresserror-code>[method]tcp-socket.finish-connect: funcself: borrow<tcp-socket>input-stream>, own<output-stream>), error-code>[method]tcp-socket.start-listen: funcStart listening for new connections.
Transitions the socket into the listening state.
Unlike POSIX, the socket must already be explicitly bound.
invalid-state: The socket is not bound to any local address. (EDESTADDRREQ)invalid-state: The socket is already in the connected state. (EISCONN, EINVAL on BSD)invalid-state: The socket is already in the listening state.address-in-use: Tried to perform an implicit bind, but there were no ephemeral ports available. (EADDRINUSE)not-in-progress: A listen operation is not in progress.would-block: Can't finish the operation, it is still in progress. (EWOULDBLOCK, EAGAIN)Unlike in POSIX, in WASI the listen operation is async. This enables
interactive WASI hosts to inject permission prompts. Runtimes that
don't want to make use of this ability can simply call the native
listen as part of either start-listen or finish-listen.
self: borrow<tcp-socket>error-code>[method]tcp-socket.finish-listen: funcself: borrow<tcp-socket>error-code>[method]tcp-socket.accept: funcAccept a new client socket.
The returned socket is bound and in the connected state. The following properties are inherited from the listener socket:
address-familykeep-alive-enabledkeep-alive-idle-timekeep-alive-intervalkeep-alive-counthop-limitreceive-buffer-sizesend-buffer-sizeOn success, this function returns the newly accepted client socket along with a pair of streams that can be used to read & write to the connection.
invalid-state: Socket is not in the listening state. (EINVAL)would-block: No pending connections at the moment. (EWOULDBLOCK, EAGAIN)connection-aborted: An incoming connection was pending, but was terminated by the client before this listener could accept it. (ECONNABORTED)new-socket-limit: The new socket resource could not be created because of a system limit. (EMFILE, ENFILE)self: borrow<tcp-socket>tcp-socket>, own<input-stream>, own<output-stream>), error-code>[method]tcp-socket.local-address: funcGet the bound local address.
POSIX mentions:
If the socket has not been bound to a local name, the value stored in the object pointed to by
addressis unspecified.
WASI is stricter and requires local-address to return invalid-state when the socket hasn't been bound yet.
invalid-state: The socket is not bound to any local address.self: borrow<tcp-socket>ip-socket-address, error-code>[method]tcp-socket.remote-address: funcGet the remote address.
invalid-state: The socket is not connected to a remote address. (ENOTCONN)self: borrow<tcp-socket>ip-socket-address, error-code>[method]tcp-socket.is-listening: funcWhether the socket is in the listening state.
Equivalent to the SO_ACCEPTCONN socket option.
self: borrow<tcp-socket>[method]tcp-socket.address-family: funcWhether this is a IPv4 or IPv6 socket.
Equivalent to the SO_DOMAIN socket option.
self: borrow<tcp-socket>[method]tcp-socket.set-listen-backlog-size: funcHints the desired listen queue size. Implementations are free to ignore this.
If the provided value is 0, an invalid-argument error is returned.
Any other value will never cause an error, but it might be silently clamped and/or rounded.
not-supported: (set) The platform does not support changing the backlog size after the initial listen.invalid-argument: (set) The provided value was 0.invalid-state: (set) The socket is in the connect-in-progress or connected state.self: borrow<tcp-socket>value: u64error-code>[method]tcp-socket.keep-alive-enabled: funcEnables or disables keepalive.
The keepalive behavior can be adjusted using:
keep-alive-idle-timekeep-alive-intervalkeep-alive-count
These properties can be configured while keep-alive-enabled is false, but only come into effect when keep-alive-enabled is true.Equivalent to the SO_KEEPALIVE socket option.
self: borrow<tcp-socket>bool, error-code>[method]tcp-socket.set-keep-alive-enabled: funcself: borrow<tcp-socket>value: boolerror-code>[method]tcp-socket.keep-alive-idle-time: funcAmount of time the connection has to be idle before TCP starts sending keepalive packets.
If the provided value is 0, an invalid-argument error is returned.
Any other value will never cause an error, but it might be silently clamped and/or rounded.
I.e. after setting a value, reading the same setting back may return a different value.
Equivalent to the TCP_KEEPIDLE socket option. (TCP_KEEPALIVE on MacOS)
invalid-argument: (set) The provided value was 0.self: borrow<tcp-socket>duration, error-code>[method]tcp-socket.set-keep-alive-idle-time: funcself: borrow<tcp-socket>value: durationerror-code>[method]tcp-socket.keep-alive-interval: funcThe time between keepalive packets.
If the provided value is 0, an invalid-argument error is returned.
Any other value will never cause an error, but it might be silently clamped and/or rounded.
I.e. after setting a value, reading the same setting back may return a different value.
Equivalent to the TCP_KEEPINTVL socket option.
invalid-argument: (set) The provided value was 0.self: borrow<tcp-socket>duration, error-code>[method]tcp-socket.set-keep-alive-interval: funcself: borrow<tcp-socket>value: durationerror-code>[method]tcp-socket.keep-alive-count: funcThe maximum amount of keepalive packets TCP should send before aborting the connection.
If the provided value is 0, an invalid-argument error is returned.
Any other value will never cause an error, but it might be silently clamped and/or rounded.
I.e. after setting a value, reading the same setting back may return a different value.
Equivalent to the TCP_KEEPCNT socket option.
invalid-argument: (set) The provided value was 0.self: borrow<tcp-socket>u32, error-code>[method]tcp-socket.set-keep-alive-count: funcself: borrow<tcp-socket>value: u32error-code>[method]tcp-socket.hop-limit: funcEquivalent to the IP_TTL & IPV6_UNICAST_HOPS socket options.
If the provided value is 0, an invalid-argument error is returned.
invalid-argument: (set) The TTL value must be 1 or higher.self: borrow<tcp-socket>u8, error-code>[method]tcp-socket.set-hop-limit: funcself: borrow<tcp-socket>value: u8error-code>[method]tcp-socket.receive-buffer-size: funcThe kernel buffer space reserved for sends/receives on this socket.
If the provided value is 0, an invalid-argument error is returned.
Any other value will never cause an error, but it might be silently clamped and/or rounded.
I.e. after setting a value, reading the same setting back may return a different value.
Equivalent to the SO_RCVBUF and SO_SNDBUF socket options.
invalid-argument: (set) The provided value was 0.self: borrow<tcp-socket>u64, error-code>[method]tcp-socket.set-receive-buffer-size: funcself: borrow<tcp-socket>value: u64error-code>[method]tcp-socket.send-buffer-size: funcself: borrow<tcp-socket>u64, error-code>[method]tcp-socket.set-send-buffer-size: funcself: borrow<tcp-socket>value: u64error-code>[method]tcp-socket.subscribe: funcCreate a pollable which can be used to poll for, or block on,
completion of any of the asynchronous operations of this socket.
When finish-bind, finish-listen, finish-connect or accept
return error(would-block), this pollable can be used to wait for
their success or failure, after which the method can be retried.
The pollable is not limited to the async operation that happens to be
in progress at the time of calling subscribe (if any). Theoretically,
subscribe only has to be called once per socket and can then be
(re)used for the remainder of the socket's lifetime.
See https://github.com/WebAssembly/wasi-sockets/blob/main/TcpSocketOperationalSemantics.md#pollable-readiness for more information.
Note: this function is here for WASI 0.2 only.
It's planned to be removed when future is natively supported in Preview3.
self: borrow<tcp-socket>pollable>[method]tcp-socket.shutdown: funcInitiate a graceful shutdown.
receive: The socket is not expecting to receive any data from
the peer. The input-stream associated with this socket will be
closed. Any data still in the receive queue at time of calling
this method will be discarded.send: The socket has no more data to send to the peer. The output-stream
associated with this socket will be closed and a FIN packet will be sent.both: Same effect as receive & send combined.This function is idempotent; shutting down a direction more than once
has no effect and returns ok.
The shutdown function does not close (drop) the socket.
invalid-state: The socket is not in the connected state. (ENOTCONN)self: borrow<tcp-socket>shutdown-type: shutdown-typeerror-code>type network
type error-code
type ip-address-family
type tcp-socket
create-tcp-socket: funcCreate a new TCP socket.
Similar to socket(AF_INET or AF_INET6, SOCK_STREAM, IPPROTO_TCP) in POSIX.
On IPv6 sockets, IPV6_V6ONLY is enabled by default and can't be configured otherwise.
This function does not require a network capability handle. This is considered to be safe because
at time of creation, the socket is not bound to any network yet. Up to the moment bind/connect
is called, the socket is effectively an in-memory configuration object, unable to communicate with the outside world.
All sockets are non-blocking. Use the wasi-poll interface to block on asynchronous operations.
not-supported: The specified address-family is not supported. (EAFNOSUPPORT)new-socket-limit: The new socket resource could not be created because of a system limit. (EMFILE, ENFILE)address-family: ip-address-familytcp-socket>, error-code>type pollable
type network
type error-code
type ip-address
resource resolve-address-streamresolve-addresses: funcResolve an internet host name to a list of IP addresses.
Unicode domain names are automatically converted to ASCII using IDNA encoding. If the input is an IP address string, the address is parsed and returned as-is without making any external requests.
See the wasi-socket proposal README.md for a comparison with getaddrinfo.
This function never blocks. It either immediately fails or immediately
returns successfully with a resolve-address-stream that can be used
to (asynchronously) fetch the results.
invalid-argument: name is a syntactically invalid domain name or IP address.resolve-address-stream>, error-code>[method]resolve-address-stream.resolve-next-address: funcReturns the next address from the resolver.
This function should be called multiple times. On each call, it will
return the next address in connection order preference. If all
addresses have been exhausted, this function returns none.
This function never returns IPv4-mapped IPv6 addresses.
name-unresolvable: Name does not exist or has no suitable associated IP addresses. (EAI_NONAME, EAI_NODATA, EAI_ADDRFAMILY)temporary-resolver-failure: A temporary failure in name resolution occurred. (EAI_AGAIN)permanent-resolver-failure: A permanent failure in name resolution occurred. (EAI_FAIL)would-block: A result is not available yet. (EWOULDBLOCK, EAGAIN)self: borrow<resolve-address-stream>ip-address>, error-code>[method]resolve-address-stream.subscribe: funcCreate a pollable which will resolve once the stream is ready for I/O.
Note: this function is here for WASI 0.2 only.
It's planned to be removed when future is natively supported in Preview3.
self: borrow<resolve-address-stream>pollable>WASI Random is a random data API.
It is intended to be portable at least between Unix-family platforms and Windows.
get-random-bytes: funcReturn 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.
get-random-u64: funcReturn 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.
The insecure interface for insecure pseudo-random numbers.
It is intended to be portable at least between Unix-family platforms and Windows.
get-insecure-random-bytes: funcReturn len insecure pseudo-random bytes.
This function is not cryptographically secure. Do not use it for anything related to security.
There are no requirements on the values of the returned bytes, however implementations are encouraged to return evenly distributed values with a long period.
get-insecure-random-u64: funcReturn an insecure pseudo-random u64 value.
This function returns the same type of pseudo-random data as
get-insecure-random-bytes, represented as a u64.
The insecure-seed interface for seeding hash-map DoS resistance.
It is intended to be portable at least between Unix-family platforms and Windows.
insecure-seed: funcReturn a 128-bit value that may contain a pseudo-random value.
The returned value is not required to be computed from a CSPRNG, and may even be entirely deterministic. Host implementations are encouraged to provide pseudo-random values to any program exposed to attacker-controlled content, to enable DoS protection built into many languages' hash-map implementations.
This function is intended to only be called once, by a source language to initialize Denial Of Service (DoS) protection in its hash-map implementation.
This will likely be changed to a value import, to prevent it from being called multiple times and potentially used for purposes other than DoS protection.