Skip to content
New issue

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

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

Already on GitHub? # to your account

rapid fire message order #1

Open
kfatehi opened this issue Dec 11, 2016 · 2 comments
Open

rapid fire message order #1

kfatehi opened this issue Dec 11, 2016 · 2 comments

Comments

@kfatehi
Copy link
Member

kfatehi commented Dec 11, 2016

all messages arrive, but the order is not guaranteed

screen shot 2016-12-10 at 6 00 51 pm

@AndrewJDR
Copy link
Collaborator

AndrewJDR commented Dec 11, 2016

I believe the original imessage timestamps coming from apple are correct even though apple sends them out of order, so I presume http://matrix.org/docs/spec/application_service/unstable.html#timestamp-massaging could help with this. i.e. if it were possible to provide a origin_server_ts value, the proper message reordering would ultimately occur, even if the messages were handled by the bridge out-of-order?

Ultimately, does using origin_server_ts seem like the proper way to handle this, @ara4n @kegsay? Also see https://github.com/matrix-org/matrix-doc/issues/698

@kfatehi
Copy link
Member Author

kfatehi commented Dec 13, 2016

kfatehi added a commit that referenced this issue May 13, 2017
message order produced by transcript reader does not make a difference.
# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants