How to use DMQ (Dead message Queue) eligibility flag in solace for any protocol bindings
manzarul opened this issue · 2 comments
Reason/Context
Please try answering few of those questions
- Why we need this improvement?
- How as a producer i will add this flag in my AsyncAPI document to reflect whether as a publisher i am publishing a message as DMQ eligibility as true?
- Example for other binding can be found here: https://github.com/asyncapi/bindings/tree/master/solace
- How will this change help?
- Help in producer and consumer contract guide (AsyncAPI spec)
- What is the motivation?
- Make it more transparent and reusable
Description
Please try answering few of those questions
- What changes have to be introduced?
- Will this be a breaking change?
- How could it be implemented/designed?
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.
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 ❤️