1. Client-server interactions in Mobile Applications

2. 2 Socket programming with TCP Example client-server app: 1) client reads line from standard input ( inFromUser stream), sends to server via socket ( outToServer stream) 2) server reads line from socket 3) server converts line to uppercase, sends back to client 4) client reads, prints modified line from socket ( inFromServer stream) Client process client TCP socket

3. 3 Client/server socket interaction: TCP wait for incoming connection request connectionSocket = welcomeSocket.accept() create socket, port= x, for incoming request: welcomeSocket = ServerSocket() create socket, connect to hostid, port= x clientSocket = Socket() close connectionSocket read reply from clientSocket close clientSocket Server (running on hostid ) Client send request using clientSocket read request from connectionSocket write reply to connectionSocket TCP connection setup

4. XML-RPC remote procedure call protocol, created in 1998 specification and a set of implementations, allowing procedure calls over the Internet calls are transported using HTTP, and encoded in XML. simple security model, can authenticate through HTTP/HTTPS

5. Allows one method of serialization Still in use, although newer technologies exist; JSON-RPC, SOAP and others. www.xmlrpc.com

6. Disadvantages XML can be slow and cumbersome in transporting and processing messages Calls can be made with plain XML instead; XML-RPC doesn't add any additional value

7. Implementations: Client: Android XML-RPC Thin, but complete XML-RPC library http://code.google.com/p/an droid-xmlrpc/ Server: Apache XML-RPC Servlet http://ws.apache.org/xmlrpc/ server.html

8. SOAP Simple Object Access Protol: is a protocol specification for exchanging structured information in the implementation of Web Services in computer networks.

9. SOAP

10. Advantage – Allow for the use of different transport protocols (HTTP as a transport protocol, but other protocols such as JMS and SMTP are also usable) – Since the SOAP model tunnels fine in the HTTP get/response model, it can tunnel easily over existing firewalls and proxies. – Can extend the existing infrastructure. Disadvantage – Since SOAP bases on XML format, it require lots of resource for parsing and processing XML file (especially for large XML file). – SOAP is very verbose, and contains lots of overhead.  Not the best choice for data exchange with mobile devices.

11. JSON JavaScript Object Notation – language independent specification of interchanging data in human-readable format. In contrast with XML-RPC and SOAP it allows for bidirectional communication between client and server (like peers) and for multiple calls. Data introduced in key:value pair format. More economical than XML in terms of data size, but has less readability. Android has JSONArray, JSONObject, JSONStringer and JSONTokener objects for parsing this format.

12. Protocol Buffers Protocol Buffers– language independent data-serialization format developed by Google. This protocol is usually applied in server-to-server interactions. Is significant faster and smaller than XML. Type of messages is defined in.proto files. Message is small logical record of a pairs of names and values. Transmitted information is encoded into binary format. Google provide necessary tools for binding this protocol with C++, Java and Python.

13. Comparison of protocols “Using Internet data in Android applications” by Michael Galpin, IBM 2010, http://www.ibm.com/developerworks/opensource/library/x- dataAndroid/index.html