QoS Service for Messages
- Dominant language
- TypeScript
- Stars
- 147
- Forks
- 96
- Avg merge
- 19h 28m
- Merged PRs (30d)
- 87
Description
### Is your feature request related to a problem? Please describe.
It is difficult to say currently that will my message be delivered at least once / only once / no tracking
### Describe the solution you'd like
I don understand we have ack feature, but will it be possible to set QoS in message so as to identify that my following message will be delivered at least once or only once & there could be different charges on top of it
### Additional context
Something similar to MQTT over WS has
Contributor guide
No contributing guide indexed for this repository
Research direction
The issue names no files, tests, or entry points. Start by reviewing the existing ack feature and the MQTT-over-WebSocket QoS behavior referenced in the request. Done would require an agreed design for delivery guarantees, message-level QoS, and any associated charges.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- azure
- Domain
- distributed-systems
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100