1 Risposta
- Più recenti
- Maggior numero di voti
- Maggior numero di commenti
0
Hi Eyal,
The problem is likely not a time out but the fact that the demo code is not designed to handle more than 1 in-flight update to shadow documents. The ulClientToken
variable is global and can only store one value: if the second publish happens before the reception of the accepted/rejected messages for the first publish, its value gets overwritten. You could modify the sample to use a set/map/list to store all the pending client tokens and match them to the received client token in prvIncomingPublishUpdateAcceptedCallback
.
Cheers,
Massimiliano
Contenuto pertinente
- AWS UFFICIALEAggiornata 3 anni fa
- AWS UFFICIALEAggiornata 3 anni fa