95-702 Distributed Systems

Lecture 8 Chapter 4: Inter-process Communications
95-702 Distributed Systems Information System Management

1

Middleware layers
Applications, services RMI and RPC This chapter request-reply protocol marshalling and external data representation UDP and TCP Middleware layers

95-702 Distributed Systems Information System Management

2

Marshalling and External Data Representation
Messages consist of sequences of bytes. Interoperability Problems Big-endian, little-endian byte ordering Floating point representation Character encodings (ASCII, UTF-8, Unicode, EBCDIC) So, we must either: Have both sides agree on an external representation or transmit in the sender’s format along with an indication of the format used. The receiver converts to its form.
95-702 Distributed Systems Information System Management

3

External Data Representation and Marshalling
External data representation – an agreed standard for the representation of data structures and primitive values Marshalling – the process of taking a collection of data items and assembling them into a form suitable for transmission in a message Unmarshalling – is the process of disassembling them on arrival into an equivalent representation at the destination The marshalling and unmarshalling are intended to be carried out by the middleware layer
95-702 Distributed Systems Information System Management

4

External Data Representation and Marshalling Quiz: Suppose we write a Java TCP client and server.NET client? 95-702 Distributed Systems Information System Management 5 . would the server interoperate with a . And suppose we we pass java objects rather than simple characters.

Java on both sides or . verbose when compared to binary but more interoperable.Net Remoting Object Serialization are both platform specific (that is. 95-702 Distributed Systems Information System Management 6 .Net on both sides) and binary.Three Important Approaches To External Data Representation and Marshalling: CORBA’s CDR binary data may be used by different programming languages Java and . XML is a textual format.

What does it look like in memory? 00000000000000000000000000000011 How could we write it to the wire? Little-Endian approach Big-Endian Approach Write 00000011 Write 0000000 Then 00000000 Then 0000000 Then 00000000 Then 0000000 Then 00000000 Then 0000011 95-702 Distributed Systems Information System Management The receiver had better know which one we are using! 7 .Interoperability Consider int j = 3.

The character ‘3’ is coded as 0000000000110011 Binary is better for arithmetic. The character ‘Ω’ is coded as 0000001110101001 The number 43 can be written as a 32 bit binary integer or as two 16 bit Unicode characters 95-702 Distributed Systems Information System Management The receiver had better know which one we are using! 8 . j holds a binary representation 00…011 We could also write it in Unicode.Binary vs. Unicode Consider int j = 3.

Let’s Examine Three Approaches to external data representation •  CORBA’s Common Data Representation •  Java’s serialization •  Web Service use of XML 95-702 Distributed Systems Information System Management 9 .

95-702 Distributed Systems Information System Management 10 . •  Values are transmitted in sender’s byte ordering which is specified in each message. •  May be used for arguments or return values in RMI. •  The data is represented in binary form.CORBA Common Data Representation (CDR) for constructed types Type sequence string array struct enumerated union Representat on i length unsigned ong) followed by elements in order ( l length unsigned ong) followed by characters i order (can also ( l n can have wi de haracters) c array elements in order (no length specified because it is fixed) in the order of declarati n of t he omponents o c unsigned ong (the values are pecified by the rder decl red) l s o a type tag followed by t e selected member h •  Can be used by a variety of programming languages.

1934} In CORBA.CORBA CDR message index in sequence of bytes 0–3 4–7 8–11 12–15 16–19 20-23 24–27 4 bytes 5 "Smit" "h___" 6 "Lond" "on__" 1934 notes on representation length of string ‘Smith’ length of string ‘London’ unsigned long struct with value: {‘Smith’. ‘London’. it is assumed that the sender and receiver have common knowledge of the order and types of the data items to be transmitted in a message. 95-702 Distributed Systems Information System Management 11 .

long year. generates Appropriate marshalling and unmarshalling operations 95-702 Distributed Systems Information System Management 12 .CORBA CORBA Interface Definition Language (IDL) CORBA Interface Compiler struct Person { string name. }. string place.

private int year.year = year. private String place. this. public Person(String nm.Java Serialization public class Person implements Serializable { private String name. year) { nm = name.place = place. } // more methods } 95-702 Distributed Systems Information System Management 13 . this. place.

May be used to store an object to disk .The serialized object holds Class information as well as object instance data .There is enough class information passed to allow Java to load the appropriate class at runtime.Java Serialization Serialization refers to the activity of flattening an object or even a connected set of objects . It may not know before hand what type of object to expect 95-702 Distributed Systems Information System Management 14 .May be used to transmit an object as an argument or return value in Java RMI .

type and name of name: place: instance variables 6 London h1 values of instance variables The true serialized form contains additional type markers.lang. 1934} 95-702 Distributed Systems Information System Management 15 . version number java.String java. ‘London’.String number. h0 and h1 are handles are references to other locations within the serialized form The above is a binary representation of {‘Smith’.lang.Java Serialized Form Serialized values Person 3 1934 8-byte version number h0 int year 5 Smith Explanation class name.

•  Verbose but can be compressed.g. •  An XSD document may be used to describes the structure and type of the data. •  Standards and tools still under development in a wide range of domains. pictures and encrypted elements) may be represented in Base64 notation. •  How? Binary data (e. 95-702 Distributed Systems Information System Management 16 . •  Messages may be constrained by a grammar written in XSD. •  Interoperable! A wide variety of languages and platforms support the marshalling and un-marshalling of XML messages.andrew.Web Service use of XML <p:person p:id=“123456789” xmlns:p=“http://www.edu/~mm6”> <p:name>Smith</p:name> <p:place>London</p:place> <p:year>1934</p:year> </p:person> •  Textual representation is readable by editors like Notepad or Textedit.cmu. •  But can represent any information found in binary messages.

But what about passing pointers? In systems such as Java RMI or CORBA or . Quiz: Why is it not enough to pass along a heap address? 95-702 Distributed Systems Information System Management 17 .NET remoting. we need a way to pass pointers to remote objects.

Representation of a Remote Object Reference 32 bits 32 bits 32 bits time 32 bits object number interface of remote object Internet address port number A remote object reference is an identifier for a remote object. How do these references differ from local references? 95-702 Distributed Systems Information System Management 18 . May be returned by or passed to a remote method in Java RMI.

But how does the middleware carry out the communication? 95-702 Distributed Systems Information System Management 19 . we know how to pass messages and addresses of objects.A Request Reply Protocol OK.

UDP Style Request-Reply Communication Client Server doOperation Request message getRequest select object execute method sendReply (wait) Reply message (continuation) 95-702 Distributed Systems Information System Management 20 .

b=getRequest() operate sendReply() public void sendReply (byte[] reply. InetAddress clientHost. 95-702 Distributed Systems Information System Management 21 .UDP Based Request-Reply Protocol Client side b = doOperation Client side: public byte[] doOperation (RemoteObjectRef o. Server side: Server side: public byte[] getRequest (). byte[] arguments) sends a request message to the remote object and returns the reply. The arguments specify the remote object. int clientPort). int methodId. the method to be invoked and the arguments of that method. sends the reply message reply to the client at its Internet address and port. acquires a client request via the server port.

return to caller passing an error message -.but perhaps the request was received and the response was lost. so.Failure Model of UDP Request side Reply ProtocolClientdoOperation b= A UDP style doOperation may timeout while waiting. What should it do? -. we might write the client to try and try until convinced that the receiver is down In the case where we retransmit messages the Server side: server may receive duplicates 95-702 Distributed Systems Information System Management b=getRequest() operate sendReply() 22 .

•  The protocol may be designed so that either (a) it re-computes the reply (in the case of idempotent operations) or (b) it returns a duplicate reply from its history of previous replies •  Acknowledgement from client clears the history 95-702 Distributed Systems Information System Management 23 .Failure Model Handling Duplicates (Appropriate for UDP but not TCP) •  Suppose the server receives a duplicate messages.

Request-Reply Message Structure messageType requestId objectReference methodId arguments int (0=Request. 1= Reply) int RemoteObjectRef int or Method array of bytes 95-702 Distributed Systems Information System Management 24 .

RPC Exchange Protocols Identified by Spector[1982] Name Client R RR RRA Request Request Request Messages sent by Server Client Reply Reply Acknowledge reply R= no response is needed and the client requires no confirmation RR= a server’s reply message is regarded as an acknowledgement RRA= Server may discard entries from its history 95-702 Distributed Systems Information System Management 25 .

A Quiz Why is TCP chosen for request-reply protocols? Variable size parameter lists. TCP works hard to ensure that messages are delivered reliably. no need to worry over retransmissions. The middleware is easier to write. filtering of duplicates or histories. So. 95-702 Distributed Systems Information System Management 26 .

1 HTTP Is Implemented over TCP. 95-702 Distributed Systems Information System Management 27 .SomeLoc/?age=23 HTTP version headers message body HTTP/ 1.HTTP Request Message Traditional HTTP request method URL or pathname GET //www.

95-702 Distributed Systems Information System Management 28 .1 <SOAP-ENV <age>23… HTTP is extensible.HTTP SOAP Message Web Services style HTTP request method URL or pathname HTTP version headers message body POST //SomeSoapLoc/server HTTP/ 1.

Traditional HTTP Reply Message HTTP version HTTP/1.1 status code reason headers message body 200 OK <html>… 95-702 Distributed Systems Information System Management 29 .

1 status code reason headers message body 200 OK <?xml version.HTTP Web Services SOAP Reply Message HTTP version HTTP/1.. 95-702 Distributed Systems Information System Management 30 .

java stub CoolClass_Stub.java skeleton MyCool_Skeleton.java Interface MyCoolClass.8 LowLevelDistributedObjectProject LowLevelDistributedObjectProjectClient 95-702 Distributed Systems Information System Management 31 .A Working Toy Example Server side code: servant MyCoolClassServant.java server CoolClassServer.java Client side code: Client CoolClient.java interface MyCoolClass.java Netbeans 6.

out.serve().CoolClassServer. MyCool_Skeleton cs = new MyCool_Skeleton(new MyCoolClass_Servant()). } } 95-702 Distributed Systems Information System Management 32 .java public class CoolClassServer { public static void main(String args[]) { System. cs.println("Main").

} } 95-702 Distributed Systems Information System Management 33 .java public class MyCoolClass_Servant implements MyCoolClass { private String n[] = {"printer". public String getDevice(String name) { for(int i = 0. private String a[] = {"HP200XT"."pda"}.equals(name)) return a[i].length."ipod"."Palm"}. } return "No device".MyCoolClass_Servant."TV"."stereo"."Panasonic". i < n. i++) { if(n[i]."Kenwood200"."Apple".

import java.net.ObjectInputStream. public MyCool_Skeleton(MyCoolClass p) { mcc = p.io.MyCool_Skeleton. public class MyCool_Skeleton { MyCoolClass mcc.ServerSocket.java (1) import java.Socket. import java. } 95-702 Distributed Systems Information System Management 34 .ObjectOutputStream. import java.io.net.

o. String result = mcc. } } catch(Throwable t) { System.accept(). String name = (String)i.getInputStream()).getOutputStream()).readObject().java (2) public void serve() { try { ServerSocket s = new ServerSocket(9000). o.getDevice(name). ObjectOutputStream o = new ObjectOutputStream(socket.println("Error " + t). while(true) { Socket socket = s. System.MyCoolSkeleton. ObjectInputStream i = new ObjectInputStream(socket.flush().out.exit(0).writeObject(result). } } } 95-702 Distributed Systems Information System Management 35 .

java // Exists on both the client and server public interface MyCoolClass { public String getDevice(String name) throws Exception.MyCoolClass. } 95-702 Distributed Systems Information System Management 36 .

out. } } } 95-702 Distributed Systems Information System Management 37 . System.println(p.java public class CoolClient { public static void main(String args[]) { try { MyCoolClass p = new CoolClass_Stub().exit(0).printStackTrace().getDevice(args[0])).CoolClient. } catch(Throwable t) { t. System.

95-702 Distributed Systems Information System Management 38 .io.io.ObjectOutputStream.net.CoolClass_Stub. import java.Socket.java (1) import java. import java. public class CoolClass_Stub implements MyCoolClass { Socket socket. ObjectInputStream i.ObjectInputStream. ObjectOutputStream o.

flush().readObject()).writeObject(name).CoolClass_Stub.getInputStream()). socket. i = new ObjectInputStream(socket. o.9000). o = new ObjectOutputStream(socket.java (2) public String getDevice(String name) throws Exception { socket = new Socket("localhost".close(). return ret. String ret = (String)(i. o.getOutputStream()). } } 95-702 Distributed Systems Information System Management 39 .

Remote references. Use of Metadata.Discussion With respect to the previous system. Reliability. let’s discuss: Request-Reply protocol. 95-702 Distributed Systems Information System Management 40 . Performance. Openness. Interoperability. Marshalling and external data representation. Security.