Loading…
A short voice session: one question, one follow-up, then instant feedback — up to 5 minutes.
Use a durable server history and a resumable synchronization cursor or sequence. A socket is a delivery channel, not the only source of message truth.
Persist the last safely applied position and request missing changes after reconnecting. Deduplicate repeated deliveries and define ordering with server-supported identifiers rather than device clocks alone. Reconcile optimistic outgoing messages with acknowledged server identities. Handle cursor expiration with a bounded resync and test disconnects during send, receive, and acknowledgment.