Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

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

Open
wants to merge 6 commits into
base: main
Choose a base branch
from
Open

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

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
6 commits
Select commit Hold shift + click to select a range
6231f8a
feat(*): Updates messaging to support request-reply
thomastaylor312 Feb 26, 2024
ba28047
feat(*): Updates interfaces to be more streamlined
thomastaylor312 May 13, 2024
18318a5
feat(*)!: Additional changes based on PR feedback
thomastaylor312 May 31, 2024
d491285
feat(types): Updates the message type to have configurable fields
thomastaylor312 Jun 12, 2024
536043d
feat(types): Renames guest config to just plain simple `config`
thomastaylor312 Jun 12, 2024
3616a2c
feat(*): Additional changes to request/reply for streamlining
thomastaylor312 Jun 13, 2024
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -45,7 +45,7 @@ Overall, the messaging interfaces aim to make it easier to build complex and sca
### Non-goals

- The messaging service interfaces do not aim to provide advanced features of message brokers, such as broker clustering, message persistence, or guaranteed message delivery. These are implementation-specific details that are not addressed by the interfaces.
- The messaging service interfaces do not aim to provide support for every possible messaging pattern or use case. Instead, they focus on the common use cases of pub-sub and push-based message delivery. Other messaging patterns, such as request-reply or publish-confirm-subscribe, are outside the scope of the interfaces.
- The messaging service interfaces do not aim to provide support for every possible messaging pattern or use case. Instead, they focus on the common use cases of pub-sub, push-based message delivery, and request-reply. Other messaging patterns, such as publish-confirm-subscribe, are outside the scope of the interfaces.
- The messaging service interfaces do not aim to provide a specific implementation of a message broker. Instead, they provide a standard way to interact with any message broker that supports the interfaces.

### API walk-through
Expand Down
178 changes: 0 additions & 178 deletions examples.md
View file
Open in desktop

This file was deleted.

Loading
Loading