crossbario / crossbario/autobahn-python
Acknowledged delivery: semantics
Open
Nobody has claimed this yet.
feature
needs-discussion
wamp
- Dominant language
- Python
- Stars
- 2.5k
- Forks
- 768
- PR merge metrics
- No merged PRs in 30d
Description
What semantics should "acknowledged event delivery" have?
An EVENT is to be answered by EVENT_RECEIVED
- .. as soon as the event was received (that is potentially even before the user subscription handler fires)
- .. after the user subscription handler has ended (regardless whether that user code did raise or not)
- .. after the user subscription handler has ended - but only if it ended successfully
- .. after the user subscription handler has ended - and the EVENT_RECEIVED contains a flag indicating the success/failure of the user subscription handler
Depending on what we chose for above (what semantics does MQTT has?), we then might want to change the name of the new WAMP message (EVENT_DELIVERED, EVENT_PROCESSED)
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Review the issue's nine-comment discussion and the four proposed EVENT_RECEIVED semantics. Compare the choices with the MQTT behavior referenced in the issue, then determine whether the message should be named EVENT_RECEIVED, EVENT_DELIVERED, or EVENT_PROCESSED. Done means the delivery semantics and message naming are explicitly decided.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- backend-api-design, distributed-systems
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100