Chapter 4: Inter-process Communications

Slides:



Advertisements
Similar presentations
CSE 486/586 Distributed Systems Remote Procedure Call
Advertisements

SOAP.
CSCI-1680 RPC and Data Representation Rodrigo Fonseca.
Remote Procedure Call Design issues Implementation RPC programming
Tam Vu Remote Procedure Call CISC 879 – Spring 03 Tam Vu March 06, 03.
C# and Windows Programming Application Domains and Remoting.
Distributed Object & Remote Invocation Vidya Satyanarayanan.
Exercises for Chapter 4: Interprocess Communication
Remote Procedure CallCS-4513, D-Term Remote Procedure Call CS-4513 Distributed Computing Systems (Slides include materials from Operating System.
Chapter 2: Communications
Copyright © George Coulouris, Jean Dollimore, Tim Kindberg This material is made available for private study and for direct.
CORBA Case Study By Jeffrey Oliver March March 17, 2003CORBA Case Study by J. T. Oliver2 History The CORBA (Common Object Request Broker Architecture)
OCT 1 Master of Information System Management Organizational Communications and Distributed Object Technologies Review For Midterm.
Internetworking (Contd) Chapter 4. Figure 3.26 ATM protocol layers.
CS490T Advanced Tablet Platform Applications Network Programming Evolution.
CSE331: Introduction to Networks and Security Lecture 11 Fall 2002.
OCT 1 Master of Information System Management Organizational Communications and Distributed Object Technologies Lecture 5: Distributed Objects.
Communication in Distributed Systems –Part 2
Distributed systems (NET 422) Prepared by Dr. Naglaa Fathi Soliman Princess Nora Bint Abdulrahman University College of computer.
OCT -- OCT Chapter 4 Coulouris Interprocess Communication.
EEC-681/781 Distributed Computing Systems Lecture 4 Wenbing Zhao Department of Electrical and Computer Engineering Cleveland State University
.NET Mobile Application Development Remote Procedure Call.
Slides for Chapter 4: Interprocess Communication From Coulouris, Dollimore and Kindberg Distributed Systems: Concepts and Design Edition 3, © Addison-Wesley.
Liang, Introduction to Java Programming, Seventh Edition, (c) 2009 Pearson Education, Inc. All rights reserved Chapter 3 Inter-process Communication.
1 Tuesday, December 23, 2008 If one ox could not do the job they did not try to grow a bigger ox, but used two oxen. - Grace Murray Hopper ( )
Introduction to Distributed Systems Slides for CSCI 3171 Lectures E. W
CSE 486/586 CSE 486/586 Distributed Systems Remote Procedure Call Steve Ko Computer Sciences and Engineering University at Buffalo.
Remote Procedure Call Andrew Whitaker CSE451. Remote Procedure Call RPC exposes a programming interface across machines: interface PriceService { Price.
CS425 /CSE424/ECE428 – Distributed Systems – Fall Nikita Borisov - UIUC1 Material derived from slides by I. Gupta, M. Harandi, J. Hou, S.
Introduction to Distributed Systems Slides for CSCI 3171 Lectures E. W. Grundke.
Chapter 4: Interprocess Communication‏ Pages
Serialization. Serialization is the process of converting an object into an intermediate format that can be stored (e.g. in a file or transmitted across.
Distributed Systems Concepts and Design Chapter 4.
Chapter 3: Interprocess Communication
Tanenbaum & Van Steen, Distributed Systems: Principles and Paradigms, 2e, (c) 2007 Prentice-Hall, Inc. All rights reserved Interprocess.
Distributed Programming CSCI 201L Jeffrey Miller, Ph.D. HTTP :// WWW - SCF. USC. EDU /~ CSCI 201 USC CSCI 201L.
1 Lecture 5 (part2) : “Interprocess communication” n reasons for process cooperation n types of message passing n direct and indirect message passing n.
From Coulouris, Dollimore, Kindberg and Blair Distributed Systems: Concepts and Design Edition 5, © Addison-Wesley 2012 Slides for Chapter 4: Interprocess.
Page 1 Remote Procedure Calls Paul Krzyzanowski Distributed Systems Except as otherwise noted, the content of this presentation.
COS 461 Recitation 7 Remote Procedure Calls. Let’s Look at Layers Again.
Chapter 5: Distributed objects and remote invocation Introduction Remote procedure call Events and notifications.
Distributed Objects and Remote Invocation Source: George Colouris, Jean Dollimore, Tim Kinderberg & Gordon Blair (2012). Distributed Systems: Concepts.
Remote Procedure Call RPC
Lecture 4 Mechanisms & Kernel for NOSs. Mechanisms for Network Operating Systems  Network operating systems provide three basic mechanisms that support.
Computer Science Lecture 3, page 1 CS677: Distributed OS Last Class: Communication in Distributed Systems Structured or unstructured? Addressing? Blocking/non-blocking?
G.v. Bochmann, revised Jan Comm Systems Arch 1 Different system architectures Object-oriented architecture (only objects, no particular structure)
1 Distribuerede systemer og sikkerhed – 28. februar 2002 From Coulouris, Dollimore and Kindberg Distributed Systems: Concepts and Design Edition 3, © Addison-Wesley.
Distributed Systems Information System Management Distributed Systems Lecture 8 Chapter 4: Inter-process Communications.
(C) 2003 University of ManchesterCS31010 Lecture 14: CORBA.
Distributed Systems Lecture 8 RPC and marshalling 1.
Distributed Computing & Embedded Systems Chapter 4: Remote Method Invocation Dr. Umair Ali Khan.
Topic 4: Distributed Objects Dr. Ayman Srour Faculty of Applied Engineering and Urban Planning University of Palestine.
Topic 3: Remote Invocation Dr. Ayman Srour Faculty of Applied Engineering and Urban Planning University of Palestine.
Object Interaction: RMI and RPC 1. Overview 2 Distributed applications programming - distributed objects model - RMI, invocation semantics - RPC Products.
Object Interaction: RMI and RPC 1. Overview 2 Distributed applications programming - distributed objects model - RMI, invocation semantics - RPC Products.
Introduction to Distributed Systems Slides for CSCI 3171 Lectures E. W. Grundke.
03 – Remote invoaction Request-reply RPC RMI Coulouris 5
Prof. Leonardo Mostarda University of Camerino
Chapter 5 Remote Procedure Call
CSE 486/586 Distributed Systems Remote Procedure Call
Layered Architectures
Edition 5, © Addison-Wesley 2012
Distributed Systems Course Topics in distributed objects
Chapter 4: Inter-process Communications
Lecture 4: RPC Remote Procedure Call Coulouris et al: Chapter 5
Lecture 4: RPC Remote Procedure Call CDK: Chapter 5
William Stallings Data and Computer Communications
Distribution Infrastructures
Remote invocation (call)
Last Class: Communication in Distributed Systems
Presentation transcript:

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

Objectives Understand the purpose of middleware. Understand how external data representations contribute to interoperability. Understand how external data representations contribute to speed. Understand marshalling/unmarshalling Understand CORBA’s CDR Understand Java’s serialization Understand XML and JSON Understand how remote object references may be represented. A UDP based request response protocol Failure models Discussion questions 95-702 Distributed Systems Information System Management

95-702 Distributed Systems Information System Management Middleware layers Middleware provides a higher level programming abstraction for the development of distributed systems. (Coulouris text). 95-702 Distributed Systems Information System Management

Moving values around on a network Passing values over a network may be problematic. Why? If both sides are the same (homogenous), no problem. But if the two sides differ in the way they represent data then we are faced with interoperability problems: 1. Big-endian, little-endian byte ordering may differ 2. Floating point representation may differ 3. Character encodings (ASCII, UTF-8, Unicode, EBCDIC) may differ as well. 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. Quiz: Which one of these approaches are we using in class today? Quiz: Which one of these approaches is used on WWW? 95-702 Distributed Systems Information System Management

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 usually carried out by the middleware layer 95-702 Distributed Systems Information System Management

External Data Representation and Marshalling Quiz: Suppose we write a TCP server in C++. Could we open a Java TCP connection to the server? Suppose we write a client in Java that sends a Java object to the server. Would the content of the Java object be reconstructed into C++? 95-702 Distributed Systems Information System Management

Interoperability concern: Big/Little Endian Consider int j = 3; 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 0000011 The receiver had better know which one we are using! 95-702 Distributed Systems Information System Management

Interoperability concern: Binary vs. Unicode Consider int j = 3; j holds a binary representation 00…011 We could also write it in Unicode. The character ‘3’ is coded as 0000000000110011 CPU’s like binary for integer 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 The receiver had better know which one we are using! 95-702 Distributed Systems Information System Management

Three Important Approaches to external data representation CORBA’s CDR (Common Data Representation) binary data may be used by different programming languages. Java and .Net Remoting Object Serialization are both platform specific (that is, Java on both sides or .Net on both sides) and binary. XML is a textual format, verbose and slow when compared to binary but interoperable. JSON is like XML but more compact. 95-702 Distributed Systems Information System Management 95-702 Distributed Systems Information System Management 9

Three important approaches to external data representation CORBA’s Common Data Representation Both sides have the IDL beforehand. This is similar to Google’s protocol buffers. Quiz: What does an IDL buy us? Java’s serialization Use Java serialization to marshal and un-marshal to a network or to storage. No IDL used. Web Service use of XML or JSON. In the case of XML, XSDL or WSDL may act as an IDL. 95-702 Distributed Systems Information System Management

CORBA in a Nutshell From the Object Management Group (OMG) around since the late 80’s OMG an international, open membership, not-for-profit technology standards group The CORBA effort was all about distributed objects on heterogeneous platforms. CORBA does a lot of things but central is the idea of passing around objects by value and references to objects. CORBA 2.0 uses CDR to represent all of the datatypes that may be passed as arguments to or return values from a method. 95-702 Distributed Systems Information System Management

CORBA Common Data Representation (CDR) for constructed types q ue ce l g th ( u si ed ) fo ll ow b el m nt r d ri ch a ra c te rs n o ca al so h av w de rs) rr ay le s i r ( o l en h s ci f ie d b eca us is x ru ct n t he or r o la at co mp v s a re pe y t r d ec ar ni g f we e s cte d m mb er Can be used by a variety of programming languages. The data is represented in binary form. Values are transmitted in sender’s byte ordering which is specified in each message. May be used for arguments or return values in RMI. 95-702 Distributed Systems Information System Management

Example CORBA CDR message struct with value: {‘Smith’, ‘London’, 1934} 0–3 4–7 8–11 12–15 16–19 20-23 24–27 5 "Smit" "h___" 6 "Lond" "on__" 1934 index in sequence of bytes 4 bytes notes on representation length of string ‘Smith’ ‘London’ unsigned long In CORBA, 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

95-702 Distributed Systems Information System Management CORBA CORBA Interface Definition Language (IDL) struct Person { string name; string place; long year; }; CORBA Interface Compiler generates Appropriate marshalling and unmarshalling operations One can easily include the proxy code and make calls to its methods. 95-702 Distributed Systems Information System Management

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

95-702 Distributed Systems Information System Management Java Serialization - Serialization refers to the activity of flattening an object or even a connected set of objects - May be used to store an object to disk - May be used to transmit an object as an argument or return value in Java RMI - 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. - It may not know before hand what type of object to expect 95-702 Distributed Systems Information System Management

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

95-702 Distributed Systems Information System Management Web Service use of XML <p:person xmlns:p=“http://www.andrew.cmu.edu/~mm6”> <p:name>Smith</p:name> <p:place>London</p:place> <p:year>1934</p:year> </p:person> How does the web work? (Text or binary?) (Compact messages?) Textual representation is readable by editors like Notepad or Textedit. We still need an agreement on what character encoding to use, e.g., an HTTP header might say Content-Type: text/xml; charset:ISO-8859-1; But can represent any information found in binary messages. How? Binary data (e.g. pictures and encrypted elements) may be represented in Base64 notation. Messages may be constrained by a grammar written in XSDL. An XSDL document may be used to describes the structure and type of the data. Interoperable! A wide variety of languages and platforms support the marshalling and un-marshalling of XML messages. (Compare with CORBA or Java serialization.) Verbose and slow Standards and tools still under development in a wide range of domains. 95-702 Distributed Systems Information System Management

95-702 Distributed Systems Information System Management Web Service use of JSON { “person” : { “name” : “Smith” “place”:”London” “year”:”1934”} } Textual representation is readable by editors like Notepad or Textedit. UTF-8 is the standard encoding. But can represent any information found in binary messages. How? Binary data (e.g. pictures and encrypted elements) may be represented in Base64 notation. Messages are constrained by a general grammar, see www.JSON.org Interoperable! A wide variety of languages and platforms support the marshalling and un-marshalling of JSON messages. The de-facto standard in many RESTful applications. 95-702 Distributed Systems Information System Management

In distributed OOP, we need to pass pointers… In stand alone OOP, we use pointers all the time. BigInteger x = new BigInteger(); We are pointing to objects that live on the heap. In systems such as Java RMI or CORBA or .NET remoting, we need a way to pass pointers to remote objects. We want x to point to an object living on some distant machine Quiz: Why is it not enough to pass along a heap address? Note: With web services we may make good use of URL’s - BUT we are not trying to build distributed OOP. 95-702 Distributed Systems Information System Management

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

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

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

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

Failure Model of UDP Request Reply Protocol Client side b = doOperation A UDP style doOperation may timeout while waiting. What should it do? -- return to caller passing an error message -- but perhaps the request was received and the response was lost, so, 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 may receive duplicates Server side: b=getRequest() operate sendReply() 95-702 Distributed Systems Information System Management

Failure Model for Handling Duplicates Suppose the server receives a duplicate messages. 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 An acknowledgement from the client may be used to clear the history 95-702 Distributed Systems Information System Management

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

RPC Exchange Protocols Identified by Spector[1982] m e M es sag s nt b y C li nt S r ve R qu t pl A ck no w ledg e re ply 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

95-702 Distributed Systems Information System Management Discussion Compare and contrast web services with distributed object approaches in terms of the following: - Marshalling and external data representation - Interoperability - Security - Reliability - Performance - Remote references - Full OOP - Describe how the protocols of the internet allow for heterogeneity. - Describe how middleware allows for heterogeneity. 95-702 Distributed Systems Information System Management