Android terminal and server data transfer solutions
Android Terminal three types and server transmission mode:
|
Socket Transmission |
WebService Transmission |
Post/get how to get Data |
Network implementation conditions |
Port: Specify Protocol: TCP,UDP |
Port: Specify Protocol: SOAP |
Port: Specify Protocol: HTTP |
Scope of Use |
Large data volume, simple format, and high real-time demand for transmission |
Standard Web Service interfaces, fixed interfaces, reusable applications |
HTTP form, fixed interface, Web reusable |
Transmission Pros and cons |
Fast speed and low data volume |
General speed, large data volume |
General speed, data volume generally |
Transfer format |
Custom |
Xml |
Custom (JSON) |
Development Requirements |
Client : Receive send data, complete data stitching, parsing, data integrity verification, etc. server-side : Receive send data, complete data stitching, parsing, data integrity verification, etc. |
Client : The use of third-party Web services components, stitching parameters, parsing data, the need for threading data calls, the process is complex. server-side : Creating a Web Service |
Client : Parse the data (Android has JSON parsing class). server-side : Generate HttpHandler-based ashx file interface |
Comprehensive |
Need to be re-developed, Cmwap is through proxy access to the network, socket transmission may be limited |
Good data reuse, existing WinForm, WebForm, mobile phone can be called |
Fast development, reuse of existing value-transfer pages |
Android terminal and server data transfer solution