Message Retention for un-delivered 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.
Due to network glitch will the server hold the message and till what duration until it is purged
### Describe the solution you'd like
Providing Message Retention configurable attribute, because not all scenarios require message retention feature while some scenarios require message retention feature especially when the request is transactional in nature
### Additional context
Providing slider or number field to configure the messages retention
Contributor guide
No contributing guide indexed for this repository
Research direction
No files, tests, or entry points are named. First clarify the retention semantics for undelivered messages, including the purge duration and how the configurable value should be exposed; done means an agreed configuration and documented behavior for transactional and non-retained scenarios.
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
- 25/100