Currently a project please give a thought

At present a project customer has 200 Android mobile terminal connection WiFi needs to display a table of contents change LAN a server database in real time.
Ask the server database table content once change requires 200 Android mobile terminal interface also shows the latest changes. At present, there are several ideas don't know which one is the best, no 200 terminal method to search for the test, so please benefit by mutual discussion.
Now think of the proposal are the following:

1 server using WebService to query the data table to return to the content Android terminal access timing WebService the latest data display. This implementation is simple, but the requirement is to display real-time estimation of each Android terminal may 1s to visit WebService, do not know the server can stand not?

2 Socket communication, but may also need to send a heartbeat packet, is also worried about server load problems.

3 push mechanism, I think this is the best if the server data update was pushed to the client, so the client is not necessary to data not updated frequently access server or may be in a larger time interval to access the server to reduce the server load.

You have what good advice about ah? ? ?

Started by Jonas at December 11, 2016 - 6:55 PM

Push a little better, for the mobile terminal project, heartbeat packet is unavoidable, because the terminal IP often change.
Can be between 2-5 minutes UDP heartbeat packet, are updated using TCP to send and receive data.

Posted by Stanley at December 16, 2016 - 7:21 PM

Socket feel good, that is you say the server load problems.. I have come to learn

Posted by May at December 25, 2016 - 8:07 PM

Push it, monitoring when data changes when the data is sent to the client, convenient traffic

Posted by Ellie at January 06, 2017 - 8:48 PM