Ecosyste.ms: Issues

An open API service for providing issue and pull request metadata for open source projects.

GitHub / WebAssembly/wasi-messaging issues and pull requests

#26 - Release `[email protected]`

Issue - State: open - Opened by danbugs 5 months ago - 1 comment

#25 - Update `wasi-messaging` to start using `@since` gates

Issue - State: open - Opened by danbugs 5 months ago

#24 - Simplifies wasi-messaging interface with feedback

Pull Request - State: open - Opened by danbugs 5 months ago - 1 comment

#23 - feat(*)!: Updates wasi-messaging interface with feedback

Pull Request - State: closed - Opened by thomastaylor312 9 months ago - 11 comments

#21 - feat(*): Updates messaging to support request-reply

Pull Request - State: closed - Opened by thomastaylor312 12 months ago - 2 comments

#20 - chore(*): split world to imports and re-version to `0.2.0-draft`

Pull Request - State: closed - Opened by Mossaka about 1 year ago

#19 - chore(*): Add Taylor as champion

Pull Request - State: closed - Opened by thomastaylor312 about 1 year ago - 1 comment

#18 - chore(*): convert to resources and add package version

Pull Request - State: closed - Opened by Mossaka about 1 year ago

#17 - feat(*): add semicolons to all the interfaces

Pull Request - State: closed - Opened by Mossaka about 1 year ago

#16 - How would a guest create a `wasi:messaging/messaging-types/error`?

Issue - State: closed - Opened by dicej over 1 year ago - 1 comment

#15 - Should `guest-configuration` include a `client` field?

Issue - State: closed - Opened by dicej over 1 year ago - 1 comment

#14 - Should `wasi:messaging/messaging-guest/handler` take a `channel` parameter?

Issue - State: closed - Opened by dicej over 1 year ago - 7 comments

#13 - Investigate using Native Messaging protocol for network (cloud) messaging

Issue - State: open - Opened by guest271314 over 1 year ago - 3 comments

#12 - Update wasi-messaging for upcoming WIT changes

Issue - State: closed - Opened by Mossaka over 1 year ago - 1 comment

#11 - Request: Demo without depending on Rust

Issue - State: closed - Opened by guest271314 almost 2 years ago - 1 comment

#10 - Include local use cases; remove redundant "service"

Pull Request - State: closed - Opened by guest271314 almost 2 years ago

#9 - `wasi-messaging` Refactor ft. stakeholder review

Pull Request - State: closed - Opened by danbugs almost 2 years ago - 18 comments

#8 - Current interface does not support a number of important use cases

Issue - State: closed - Opened by autodidaddict almost 2 years ago - 7 comments

#7 - Producer does not need to specify what type of a channel to send message to

Issue - State: closed - Opened by Mossaka almost 2 years ago - 3 comments

#6 - Aligning messaging interfaces

Issue - State: closed - Opened by salaboy almost 2 years ago - 1 comment

#5 - added api walkthrough section

Pull Request - State: closed - Opened by danbugs almost 2 years ago

#4 - Use case: Local usage

Issue - State: closed - Opened by guest271314 almost 2 years ago - 5 comments

#3 - preview2 alignment

Pull Request - State: closed - Opened by danbugs almost 2 years ago

#2 - updated messaging.wit.md, and README.md

Pull Request - State: closed - Opened by danbugs about 2 years ago - 6 comments

#1 - update workflow to use new wit-abi version

Pull Request - State: closed - Opened by danbugs about 2 years ago