Asyncify the API

Open
#68 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
35/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Quiet
Tech stack
wasm

Research direction

Start by reading the referenced wit/keyvalue/wit/cas.wit definition and comparing the version conventions used by wasi-otel and wasi-webgpu. Determine how the keyvalue API should build on WASI 0.3.0, including the async interface and CAS behavior. Done means the proposal is updated to the agreed 0.3.0-rc.n version with those API changes documented in the WIT definition.

Written by the indexing model from the issue text.

Description

Now that WASI 0.3.0 has been released, this proposal should build on WASI 0.3.0. I recommend setting the version to 0.3.0-rc.n as well like wasi-otel and wasi-webgpu.

I created an async keyvalue API (asyncified version of this wit definition) that additionally solves the ABA problem for CAS. This may be a good starting point: https://github.com/wasmCloud/wasmCloud/blob/main/wit/keyvalue/wit/cas.wit

Dominant language
No language data
Stars
54
Forks
18
PR merge metrics
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from WebAssembly/wasi-keyvalue

All issues in WebAssembly/wasi-keyvalue

Similar issues

More Backend & API Design issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.