The waPC suite gives you the tools to build dynamic applications with WebAssembly.

Learn More Download

The WebAssembly Procedure Call project — waPC for short — is a suite of tools and specifications that allow native code to make, receive, and forward arbitrary calls to or from WebAssembly guests.

WaPC has host implementations for Rust, Go, Node.js, and browser environments and guest libraries for Rust, Go, and AssemblyScript.

The waPC tool suite

The waPC protocol

The core of waPC is a protocol for communicating into and out of WebAssembly.

Use waPC for everything from small libraries to distributed application platforms.

waPC Hosts & Guests

waPC hosts manage the lifecycle and communication of WebAssembly guests.

Hosts and guests give you a universal interface for dynamic behavior in both native and WebAssembly.

WIDL & the waPC CLI

Use the WebAssembly Interface Definition Language (WIDL) to define your WebAssembly’s schema and the wapc CLI to generate all the code except your business logic.

How it works

waPC Host
Once initialized with a WebAssembly intepreter and a wasm binary, the wapc-host library can start executing functions in the wasm guest. The host and guest operate over the waPC communication protocol to satisfy bindings for compiled languages. This protocol takes an operation name and input data, serializes it, and calls the receiving waPC method in the wasm guest.
waPC Guest
The wasm binary — built with the wapc-guest bindings — accepts the waPC call, deserializes the input, executes the requested operation by name, serializes the return value, and passes it back over the waPC protocol back to the host.
WIDL
Your WIDL definition is the description of your wasm module's interface. It includes the exposed operations, the input types, return types, namespaces, and more. The waPC CLI uses a widl definition to generate Rust, Go, or AssemblyScript code. (see more)
waPC CLI
The waPC command line tool automates the process of creating new projects and generating waPC-compliant integration code.

Example schema.widl

namespace "my:httpserver"

interface {
  "Handles an HTTP request"
  handleRequest{request: Request}: Response
}

"Represents an HTTP request, handled by the guest module"
type Request {
  method: string
  path: string
  queryString: string
  header: {string : string}
  body: bytes?
}

"HTTP response returned from a request."
type Response {
  statusCode: u32 = 200
  status: string = "OK"
  header: {string : string}
  body: bytes?
}

Contributions welcome !