New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Is it a problem that events pushed from the server aren't acked by the client? #5

Open

ara4n opened this issue Jan 20, 2017 · 1 comment

Member

ara4n commented Jan 20, 2017

/sync provides an implicit ACK that events have been received by the client, but I think we lose that here?

Member

richvdh commented Jan 20, 2017

Yes, this is a problem now that we treat an incremental sync as an ack of to-device events in the previous sync.

We're going to need to add acks to the websockets protocol, and provide a modified sync api for the proxy to talk to the HS over.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment