Otte, R., Patrick, P., and Roy, M. (1996). Understanding CORBA: The Common Object Request Broker Architecture. Prentice-Hall.  Home/Search   Document Not in Database   Summary   Related Articles   Check

....comes from the fact each one of the overall system components embodies its own data and process management, often in an ad hoc way. The first topics seriously worked out were data interoperability, including work around database interoperability and, perhaps the most known standard, CORBA [OPR96] CORBA ambition is to define a standard representation of all data, a common agreement on the way to transfer the information and to call services over heterogeneous architecture. The goal is to make possible for a component, developed independently, to be plugged in without disturbing the ....

R. Otte, P. Patrick, and M. Roy. Understanding CORBA the Common Object Request Broker Architecture. Prentice Hall, 1996.

....commonly provide two level addressing. This provides the ability to use local and remote references interchangeably. References that arrive on a site are automatically converted to the local form if they refer to local entities. Typical examples include Java RMI [Sun Microsystems 1997] CORBA [Otte et al. 1996], and the Ericsson OTP (Open Telecom Platform) Armstrong et al. 1996; Wikstrom 1994] Two level addressing can be extended to provide weak logic variables (see also Section 2.1.4) It suffices to add an unknown state to variables: 1) threads block when the variable is unknown, 2) when the ....

Otte, R., Patrick, P., and Roy, M. 1996. Understanding CORBA: The Common Object Request Broker Architecture. Prentice-Hall PTR, Upper Saddle River, N.J.

....these properties requires specialist knowledge beyond that needed to develop an application on a single machine. For example, a new client server application can be written with Java RMI [23, 24] An existing application can be connected with another through a CORBA implementation (e.g. Orbix) [26]. Yet in both cases the tools are unsatisfactory. For example, reorganizing the distribution structure requires rewriting the application. Furthermore, with each major problem that is addressed, e.g. distribution structure, fault tolerance, security, and openness, the complexity of the ....

Randy Otte, Paul Patrick, and Mark Roy. Understanding CORBA: The Common Object Request Broker Architecture. Prentice-Hall PTR, Upper Saddle River, N.J., 1996.

....by another program [5] RPC is a typical method of close coupling. For a fast working link that has to send information in real time, close coupling is the method of choice. RPCs are often integrated among other services in a middleware. We considered several middleware standards like CORBA [6], DCE [7] DCOM [8] and Java RMI [9] as described in Section 4. We decided to use DCE (Distributed Computing Environment) because it is efficient and independent of the operating system and network. The remaining paper is structured as follows. The next two sections introduce the programs we ....

.... It is the only suite of integrated services from a vendor neutral source that enables organizations to develop, use, and maintain distributed programs across heterogeneous networks [13] We have considered alternative standards to DCE such as the Common Object Request Broker Architecture (CORBA) [6] from the Object Management Group (OMG) the Distributed Component Object Model (DCOM) 8] from Microsoft, and Java RMI (Remote Method Invocation) 9] Due to the space limitations, we omit the advantages and drawbacks of the alternative middleware standards. 4.1 Remote Procedure Call (RPC) DCE ....

R. Otte, P. Patrick, and M. Roy. Understanding CORBA: The Common Object Request Broker Architecture. Prentice Hall, Upper Saddle River, NJ, 1996.

....used in settings where there is no possibility of inconsistency. 9.2 Languages not based on logic Systems with support for distributed computing commonly provide two level addressing, namely the ability to transparently pass references between sites. Typical examples include Java RMI [20] CORBA [22], and the Ericsson OTP (Open Telecom Platform) 3, 36] This basic mechanism can be extended to provide weak logic variables (see also Section 2.1.4) 1) if the value is available, it is should be used immediately without programmer intervention, 2) threads block on availability of the value, ....

Randy Otte, Paul Patrick, and Mark Roy. Understanding CORBA: The Common Object Request Broker Architecture. Prentice-Hall PTR, Upper Saddle River, N.J., 1996.

....specifi cations from the Moving Pictures Experts Group (MPEG) standards. The former defi nes the MPEG to ATM mapping. The latter includes the specifi cation for the control functions to access a VoD server. The DSM CC architecture uses a Common Object Request Broker Architecture (CORBA) [4] as defi ned by the Object Management Group (OMG) to implementRemote Procedure Calls (RPCs) In parallel to the DAVICactivities, the Internethas beenexpandingexponentially,largely due to the popularity of the World Wide Web (WWW) Web browsers and the HyperText Markup Language (HTML) 5] make it ....

R. Otte, O.Patrick, and M. Roy, Understanding CORBA: the common object request broker architecture, Prentice Hall, 1996.

.... capture it. Figure 24: Communication fundamentals. Subscription can be expressed in terms of a message type, a name of a particular message or a message content (the values of certain message attributes) In this approach, widely used in message servers (such as Field [26] Tooltalk [27] Corba [44]) sender and receivers do not know Sender Communication Receiver Manager Controller Message Message copies (Activity agent) Activity agent) Subscribe Explicit communication Register Implicit communication Agenda Measures and versions APEL: a Graphical Yet Executable Formalism for Process ....

R. Otte, P. Patrick, and M. Roy. Understanding CORBA the Common Object Request Broker Architecture. Prentice Hall, 1996.

....tolerance. Namely, the redundancy concept introduced can be used as a basic mechanism to tolerate sites failures. 6 Related works Many systems, that we know of, except Emerald [7] and Obliq [2] do distributed execution by adding a distribution layer on top of a centralized language, i.e. CORBA [11], Erlang [15] Java [9] This has the disadvantage that distribution is not a seamless extension to the language. In Emerald, objects are stationary by default and explicit primitive operations exist to move them. Moving a mutable object is an atomic operation that clones the object on the ....

Randy Otte, Paul Patrick, and Mark Roy. Understanding CORBA: The Common Object Request Broker Architecture. Prentice-Hall PTR, Upper Saddle River, N.J., 1996.

....not based on logic Systems with support for distributed computing commonly provide two level addressing, namely the ability to transparently pass references between sites. Typical examples include Java 5 To the referees: we would be happy to be corrected on this point RMI [22] CORBA [24], and the Ericsson OTP (Open Telecom Platform) 4, 39] This basic mechanism can be extended to provide weak logic variables (see also Section 2.1.4) 1) if the value is available, it is should be used immediately without programmer intervention, 2) threads block on availability of the value, ....

Randy Otte, Paul Patrick, and Mark Roy. Understanding CORBA: The Common Object Request Broker Architecture. Prentice-Hall PTR, Upper Saddle River, N.J., 1996.

....noyaux essentiellement centralises. Les plates formes existantes (CORBA, DCE, etc. voir Section 2) sont en fait basees sur un modele de programmation centralisee. Dans CORBA, par exemple, il faut ecrire une interface en IDL pour un objet lointain, ce qui n est pas necessaire pour un objet local [27]. Les fonctionnalites reparties sont ajoutees comme des services, et il incombe au programmeur de raccorder tous ses services. Ceci rend la programmation repartie tres compliquee sur ces plates formes. Si un programmeur veut par exemple rendre son application tolerante aux pannes ou securisee, il ....

....Chorus [34] Le but de ces systemes est de donner l illusion qu un systeme reparti soit un systeme centralise, avec neanmoins plus de ressources et plus de fiabilite. 3. Couche d aide a la construction d applications reparties (Middleware) Quelques exemples representatifs sont DCE [34, 14] CORBA [27, 13], OTP [15] PVM [17] et Linda [10] La couche middleware se situe entre le systeme d exploitation et les applications. Dans le premier cas, le langage de programmation reste presque le meme, avec toutefois des annotations pour les variables ayant differents comportements repartis. Dans les cas (2) ....

[Article contains additional citation context not shown here]

Randy Otte, Paul Patrick et Mark Roy. Understanding CORBA : The Common Object Request Broker Architecture. Prentice Hall PTR, 1996.

....and communicate via a service kernel called the ORB core. Objects can alternate between client role and server role. An object is in a client role when it is the originator of an object invocation. Server objects are called object implementations. Most objects probably will play both the roles [27]. Client Object Implementation ORB Request Figure 3.1: A request being sent through the Object Request Broker. CORBA extends the idea of separating an object s client and implementation with location transparency. It provides for mechanisms to consult objects around the network without having to ....

Randy Otte, Paul Patrick, and Mark Roy. Understanding CORBA:the common object request broker architecture. Prentice-Hall, Inc., Upper Sadde River, NJ, 1996.

....evolving and complex applications. This section presents the basic concepts and properties of the CORBA architecture. 2. 1 Overview of CORBA and its Event Service A comprehensive description of CORBA would go far beyond the scope of this article, and many good books can be found on this topic [OPR96, MZ95]. Nevertheless, let us briefly describe the underlying concepts of this approach to distributed computing. The central component of the architecture is the Object Request Broker usually called ORB whose principal role consists in transparently relaying requests to objects, across the ....

Randy Otte, Paul Patrick, and Mark Roy. Understanding CORBA: The Common Object Request Broker Architecture. Prentice Hall, 1996.

....in a message require additional credit, then the message is put in a pending queue until all credit arrives. 8 Related work All systems that we know of except Emerald [31] and Obliq [10] do distributed execution by adding a distribution layer on top of a centralized language, e.g. CORBA [36, 15], DCE [45, 7] Erlang [48] Java [44] Facile [34] and Telescript [21] This has the disadvantage that distribution is not a seamless extension to the language, and therefore distributed extensions to language operations (such as mobile objects or replicated data) must be handled by explicit ....

Randy Otte, Paul Patrick, and Mark Roy. Understanding CORBA: The Common Object Request Broker Architecture. Prentice Hall PTR, 1996.

....these properties requires specialist knowledge beyond that needed to develop an application on a single machine. For example, a new client server application can be written with Java RMI [33, 34] An existing application can be connected with another through a CORBA implementation (e.g. Orbix) [37]. Yet in both cases the tools are unsatisfactory. Simply reorganizing the distribution structure requires rewriting the application. Because the Java specification does not require time sliced threads [15] doing such a reorganization in Java may require profound changes to the application. ....

Randy Otte, Paul Patrick, and Mark Roy. Understanding CORBA: The Common Object Request Broker Architecture. Prentice-Hall PTR, Upper Saddle River, N.J., 1996.

....the language must give clear meanings to replicated data and mobile objects. Haridi, Van Roy, Smolka, Distributed Oz Extending the basic language operations. All systems that we know of except Obliq [1] do distributed execution by adding a distribution layer on top of an existing language [10, 17, 18, 19]. This has the disadvantage that distribution is not a seamless extension to the language, and therefore distributed extensions to language operations (such as mobile objects or replicated data) must be handled by explicit programmer effort. A better technique is to look carefully at the basic ....

Randy Otte, Paul Patrick, and Mark Roy. Understanding CORBA: The Common Object Request Broker Architecture. Prentice Hall PTR, 1996.

....programmer. For example, the language must give clear meanings to replicated data and mobile objects. 1. 1 Extending the basic language operations All systems that we know of except Obliq [3] and Emerald [13] do distributed execution by adding a distribution layer on top of an existing language [18, 26, 27, 30]. This has the disadvantage that distribution is not a seamless extension to the language, and therefore distributed extensions to language operations (such as mobile objects or replicated data) must be handled by explicit programmer effort. A better technique is to look carefully at the basic ....

Randy Otte, Paul Patrick, and Mark Roy. Understanding CORBA: The Common Object Request Broker Architecture. Prentice Hall PTR, 1996.

....the language must give clear meanings to replicated data and mobile objects. Haridi, Van Roy, Smolka, Distributed Oz Extending the basic language operations. All systems that we know of except Obliq [1] do distributed execution by adding a distribution layer on top of an existing language [10, 17, 18, 19]. This has the disadvantage that distribution is not a seamless extension to the language, and therefore distributed extensions to language operations (such as mobile objects or replicated data) must be handled by explicit programmer eoeort. A better technique is to look carefully at the basic ....

Randy Otte, Paul Patrick, and Mark Roy. Understanding CORBA: The Common Object Request Broker Architecture. Prentice Hall PTR, 1996.

....) It then sends proceed(N z ) to thread T. 5. Thread T receives proceed(N z ) The thread then invokes the binding of N x and N z . 6 Related work All systems that we know of except Obliq [5] do distributed execution by adding a distribution layer on top of a centralized language, e.g. CORBA [21, 6], DCE [28, 3] Erlang [31] Java [27] Facile [20] and Telescript [10] This has the disadvantage that distribution is not a seamless extension to the language, and therefore distributed extensions to language operations (such as mobile objects or replicated data) must be handled by explicit ....

Randy Otte, Paul Patrick, and Mark Roy. Understanding CORBA: The Common Object Request Broker Architecture. Prentice Hall PTR, 1996.

No context found.

Otte, R., Patrick, P., and Roy, M. (1996). Understanding CORBA: The Common Object Request Broker Architecture. Prentice-Hall.

No context found.

R. Otte, P. Patrick, and M. Roy. Understanding CORBA the Common Object Request Broker Architecture. Prentice Hall, 1996.

No context found.

Randy Otte, Paul Patrick, and Mark Roy. Understanding CORBA: the common object request broker architecture. Pretice Hall, Inc., Upper Saddle River, New Jersey 07458, USA, 1st edition, 1996. 166.

No context found.

Otte et al. 96: Otte, R., Patrick, P., and Roy, M. Understanding CORBA: the Common Object Request Broker Architecture. Prentice Hall, Englewood Cliffs, New Jersey, 1996.

Online articles have much greater impact   More about CiteSeer.IST   Add search form to your site   Submit documents   Feedback  

CiteSeer.IST - Copyright Penn State and NEC