Tekijä | SHA1 | Viesti | Päivämäärä |
---|---|---|---|
|
8b30dbf46f |
Handle unparsable JSON as invalid content (#11733)
Change-Id: I67ed5e78b93ff0fe20d861105a0aa01ae6ccb2e6 |
8 vuotta sitten |
|
3e6bb5541c |
Use same reconnect logic for Push as for XHR (#17075)
* No longer queue message separately in PushConnection * Use XHR for client to server communication when using long polling (or streaming) * Websocket is used for communication in both directions Note that using XHR for client to server responses at the same time as a push connection is open means we must take into account on the client side that we may receive message in the wrong order. This will be addressed in the following change. Change-Id: I97706db3481379593e71dc5bb552727a0486692b |
9 vuotta sitten |
|
d93527f257 |
Move XHR code to XhrConnection (#11733)
* XhrConnection internally manages the URI to send to * send(JsonObject) now only takes the payload * retry logic for status 0 removed for now Change-Id: Ieca25df0ebe06773139b2bec7e9a2586df77b24d |
9 vuotta sitten |