HI, All
If we have an app client (on lots of devices) that works with HTTP API on a server with non-stable Internet connection - it's very important to make all correct that:
1) not to lose the unsent data
2) not to send unconfirmed data many times
3) not to overload the server by tons of requests (if many clients - it's easy possible)
4) sometimes during HTTP-reply parsing it needs to send another HTTP-request - confirmation or additional info getting
5) HTTP requests for CRUD: SAVE (create), LOAD (read), UPDATE and DELETE from a server database
6) some file upload or download is needed periodically, file may be big, and whole Internet connection bandwidth is occupied
7) and sure, all must wait for Internet connection restore, if missed.
I guess, all HTTP-requests must be in a one queue, fully synchronous sending. And it looks like that a STACK queue is needed here, not FIFO.
How to do it all together correctly, any suggestions?
If we have an app client (on lots of devices) that works with HTTP API on a server with non-stable Internet connection - it's very important to make all correct that:
1) not to lose the unsent data
2) not to send unconfirmed data many times
3) not to overload the server by tons of requests (if many clients - it's easy possible)
4) sometimes during HTTP-reply parsing it needs to send another HTTP-request - confirmation or additional info getting
5) HTTP requests for CRUD: SAVE (create), LOAD (read), UPDATE and DELETE from a server database
6) some file upload or download is needed periodically, file may be big, and whole Internet connection bandwidth is occupied
7) and sure, all must wait for Internet connection restore, if missed.
I guess, all HTTP-requests must be in a one queue, fully synchronous sending. And it looks like that a STACK queue is needed here, not FIFO.
How to do it all together correctly, any suggestions?
Last edited: