df51523a84
Previously messages could be sent out of order if (e.g.) 1. You're on a slow network 2. You send a big attachment 3. You immediately send text Generally in this scenario, the text will be sent before the attachment. Also, introduced a more general retry loop to retry on *any* failure during sending. Previously the only retry logic was around the messages API on the Signal Server. Now we'll also retry failures when allocating an attachment, or uploading an attachment. TODO: remove the now redundant retry logic in the message sender? TODO: there is still one place where we send messages directly through the MessageSender, rather than via the operation - when resending to a group due to a safety number change. This is separate logic because we were being sure to *only* resend to that one recipient. Cleaning this up would move a lot of code around. Once Signal-Desktop implements timestamp based de-duping we could shave that wart by having this troublesome codepath use NSOperation like everything else. // FREEBIE |
||
|---|---|---|
| .. | ||
| Account | ||
| Contacts | ||
| Devices | ||
| Messages | ||
| Network | ||
| Protocols | ||
| Security | ||
| Storage | ||
| Util | ||
| TextSecureKitEnv.h | ||
| TextSecureKitEnv.m | ||
| TSConstants.h | ||
| TSPrefix.h | ||