Skip to content
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.

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

If a message fails to send, it's annoying that subsequent ones get sent then out-of-order, where they no longer makes sense. #1502

Closed
matrixbot opened this issue May 11, 2016 · 4 comments

Comments

@matrixbot
Copy link

Created by @ matthew:matrix.org.

Surely one blocked message should block subsequent ones rather than them being delivered in the wrong order

@ara4n
Copy link
Member

ara4n commented May 24, 2016

@kegsay: was this ever intended to work with out-of-order messages okay?

@ara4n ara4n added this to the v2 - Public Preview milestone May 24, 2016
@kegsay
Copy link
Contributor

kegsay commented Jun 13, 2016

There was no special handling of out-of-order messages because it wasn't possible to get out of order messages because:

one blocked message should block subsequent ones

This was implemented. No idea what the JS SDK does now though.

@ara4n
Copy link
Member

ara4n commented Jul 29, 2016

More importantly, when queued messages are 'Resend now', they get sent in a totally arbitrary order. This is incredibly annoying.

@ara4n ara4n added P1 and removed P2 labels Jul 29, 2016
@turt2live
Copy link
Member

Duplicate of #5408 (which is now fixed)

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

No branches or pull requests

4 participants