mirror of
https://gh.wpcy.net/https://github.com/discourse/discourse.git
synced 2026-05-17 21:21:47 +08:00
a96ace858e
Uses the timestamp at the moment where the user hits send for the created_at value of the chat message. This should ensure very consistent ordering. The implementation is simple: - collects the timestamp and send it in the request (client_created_at) - if client_created_at is present and valid, set it as created_at when creating the message I suspect that we could end up in a situation where a message is routed to a slower worker and even if sent before an other message could end up being persisted before the first message which would cause ordering issues. |
||
|---|---|---|
| .. | ||
| actions | ||
| chat | ||
| hashtag_autocomplete_service_spec.rb | ||
