Which recovery design handles uncertainty after a WebSocket connection drops during a sid…

Which recovery design handles uncertainty after a WebSocket connection drops during a side-effecting message?

1. Use message IDs, acknowledgements, deduplication, resume cursors, and a bounded outbound queue.
2. Reconnect and resend every buffered message without identity or limits.
3. Assume a successful reconnect restores the old connection and its delivery state.