WASI Subgroup Ratifies 0.3.0 Release, Rebasing Interface on Native Async Primitives

The WebAssembly System Interface (WASI) Subgroup has ratified the release of version 0.3.0, a move that rebases the specification onto the native asynchronous primitives of the WebAssembly Component Model. This ratification marks a departure from the complex patterns required in version 0.2, where developers had to perform significant structural adjustments to manage asynchronous input and output. By leveraging the component model’s native async support, the new release aims to improve ergonomics and streamline the development experience for those building portable applications.

A primary technical shift in this release is the handling of network access. In previous iterations, network access was modelled as a capability resource that needed to be threaded through every bind, connect, and lookup call. Version 0.3.0 removes this resource entirely, granting network access via world imports instead. This change eliminates the need for intermediate asynchronous states such as bind-in-progress or connect-in-progress, replacing them with direct async functions. Consequently, the subscribe mechanism and pollable-driven workflows have been discarded in favour of simpler, more direct async function calls.

The specification has also undergone a significant consolidation of resource types, collapsing them from eight distinct types down to just two: request and response. Under the previous model, a complex matrix of resources existed for incoming and outgoing data across request, response, and body spaces. The new structure represents bodies directly as streams and trailers as futures. This simplification extends to UDP and TCP handling, where incoming and outgoing datagram stream resources have been replaced by plain async send and receive functions, with byte I/O now living on the socket resource’s own stream methods.

Terminology within the interface has been standardised to align with POSIX conventions and broader ecosystem standards. Terms that were specific to WASI, such as 'wall-clock' and 'datetime', have been renamed to 'system-clock' and 'instant' respectively. This change addresses inconsistencies with how other systems, including Rust’s std::time, refer to timekeeping. The wasi:clocks package and filesystem timestamps have been updated to reflect this alignment, ensuring that the interface speaks the same language as the surrounding software ecosystem.

Downstream impact is expected to be largely mechanical, involving structural updates to interface files such as stdin.wit and stdout.wit. The wasi-testsuite has already been updated to reflect these changes, demonstrating that migration will primarily involve find-and-replace operations rather than fundamental logic rewrites. A new middleware world has also been introduced to support components sitting in a request path, replacing the old proxy world and providing first-class support for middleware architectures.