matrix-org / matrix-org/matrix-websockets-proxy
Is it a problem that events pushed from the server aren't acked by the client?
Open
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 16
- Forks
- 8
- PR merge metrics
- No merged PRs in 30d
Description
/sync provides an implicit ACK that events have been received by the client, but I think we lose that here?
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
Start by comparing the /sync implicit ACK behavior with events pushed from the server over the WebSocket. Trace how the client receives each event and determine whether an acknowledgement is required; done means the expected ACK behavior is established and any missing protocol work is clearly scoped.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- api, backend
- Issue type
- Bug
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100