apache / apache/pekko-connectors
Provide API without connectionId
Open
enhancement
mqtt-streaming
- Dominant language
- Scala
- Stars
- 82
- Forks
- 50
- Avg merge
- 1d 2h
- Merged PRs (30d)
- 78
Description
Subtle bugs can appear when you use overlapping connection ids within a session.
It would be good to provide an API where the component takes care of this automatically.
Contributor guide
Research direction
The issue names no files, tests, or entry points. Start by tracing how connectionId is currently supplied and used within a session, then clarify the component-owned API and how overlapping IDs should be handled. Define completion criteria and tests with the maintainers before implementation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- scala
- Domain
- api, backend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100