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.

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

Multiple reply addresses #1052

Closed
mvuckovic opened this issue Apr 15, 2024 · 3 comments
Closed

Multiple reply addresses #1052

mvuckovic opened this issue Apr 15, 2024 · 3 comments
Labels
❔ Question A question about the spec or processes stale

Comments

@mvuckovic
Copy link

Hello!

I'm trying to document MQTT Request/Response pattern where a single Request can result in multiple channel/message replies, something similar to AWS IoT Core Shadow /shadow/get, /shadow/get/accepted, shadow/get/rejected

It seems V3 currently only supports a single reply address object. Is there any recommended way I could achieve this with the current spec?

Thanks :)

@mvuckovic mvuckovic added the ❔ Question A question about the spec or processes label Apr 15, 2024
Copy link

Welcome to AsyncAPI. Thanks a lot for reporting your first issue. Please check out our contributors guide and the instructions about a basic recommended setup useful for opening a pull request.
Keep in mind there are also other channels you can use to interact with AsyncAPI community. For more details check out this issue.

@jonaslagoni
Copy link
Member

In the current version you would have to create multiple operations where each results in a single reply 🙂 When the feature was created we never discussed that a single operation should be able to result in multiple addresses on a single operation, either through channel or reply 🤔

Copy link

This issue has been automatically marked as stale because it has not had recent activity 😴

It will be closed in 120 days if no further activity occurs. To unstale this issue, add a comment with a detailed explanation.

There can be many reasons why some specific issue has no activity. The most probable cause is lack of time, not lack of interest. AsyncAPI Initiative is a Linux Foundation project not owned by a single for-profit company. It is a community-driven initiative ruled under open governance model.

Let us figure out together how to push this issue forward. Connect with us through one of many communication channels we established here.

Thank you for your patience ❤️

@github-actions github-actions bot added the stale label Aug 14, 2024
@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale Dec 12, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
❔ Question A question about the spec or processes stale
Projects
None yet
Development

No branches or pull requests

2 participants