Write a server using Java. Provide service support for mobile apps. So, the normal transmission, is not the basic HTTP delivery JSON format of data this scheme is more?
If you need the service to push messages to the app, if you do not use a third party, is not using XAMPP to build a message server, and then the app and the message server has a long connection, then with this connection, is it possible to do not need the above HTTP service scheme? That is, can the message server replace the basic service?
The requirements for the project are certainly part of the app pull server, which is part of the server push to app.
Reply content:
Write a server using Java. Provide service support for mobile apps. So, the normal transmission, is not the basic HTTP delivery JSON format of data this scheme is more?
If you need the service to push messages to the app, if you do not use a third party, is not using XAMPP to build a message server, and then the app and the message server has a long connection, then with this connection, is it possible to do not need the above HTTP service scheme? That is, can the message server replace the basic service?
The requirements for the project are certainly part of the app pull server, which is part of the server push to app.
1. The mainstream is also based on the HTTP protocol, JSON format data;
2. About push, recommend a good blog post (push back is more troublesome things, third-party push is to solve this "trouble" problem).
In the current situation (Android platform), it is almost impossible to maintain long connections in the background. Or HTTP-based, can not be used long-connection push to do not use. There is really push demand, with a third-party bar save time and effort ... Don't rely on the backstage to push, this is a grudge.