Movatterモバイル変換


[0]ホーム

URL:


Mayuresh Wadekar, profile picture
Uploaded byMayuresh Wadekar
PPT, PDF15,370 views

Distributed objects & components of corba

This document discusses distributed objects and CORBA (Common Object Request Broker Architecture). It defines distributed objects as software modules that reside across multiple computers but work together. CORBA allows distributed objects written in different languages to communicate. It includes an Object Request Broker that acts as middleware to relay requests between client objects and server implementations. CORBA uses interface definition language (IDL) to define interfaces independently of programming languages. It also includes client stubs, server skeletons, an interface repository, and implementation repository to enable communication between distributed objects.

Embed presentation

Downloaded 474 times
Distributed Objects & ComponentsCORBAPresented By :Mayuresh Wadekar (52)Ajay Yadav (53)
Distributed SystemDistributed System• Distributed System referred to computer networks where individualcomputers were physically distributed within some geographicalarea.Fig A. Difference Between Distributed & Parallel Computing
Distributed ObjectDistributed Object• Distributed objects refers to software modules that are designed towork together, but reside either in multiple computers connectedvia a network or in different processes inside the same computerFig B. Distributed objects residing in different machines.
Working of Distributed ObjectsWorking of Distributed ObjectsFig C. Working of Distributed Objects
Remote InvocationRemote InvocationFig D: Remote Invocation & Local Invocation
DISTRIBUTED OBJECTSDISTRIBUTED OBJECTS• Remote object references:Globally unique reference for a distributed objects maybe passed as a parameter.• Distributed actions:Initiated by a method invocation, potentially resulting ininvocation chains.• Distributed exceptions:Additional exceptions generated from the distributednature of the system, including message loss or processfailure
DISTRIBUTED OBJECTSDISTRIBUTED OBJECTS• Remote interfaces:Provides an abstract specification of the methods thatcan be invoked on the remote object.Fig D. Remote Interfaces
EVOLUTION OF DISTRIBUTED OBJECTSEVOLUTION OF DISTRIBUTED OBJECTS• Distributed objects as a natural evolution from threestrands of activity:1. Distributed systems:Earlier middleware was based on the client-server modeland there was a desire for more sophisticated programmingabstractions.2. Programming languages:Earlier work in object-oriented languages such as Simula-67and Smalltalk led to the emergence of more mainstream andheavily. Used programming languages such as Java and C++
EVOLUTION OF DISTRIBUTED OBJECTSEVOLUTION OF DISTRIBUTED OBJECTSFig E: OOP Distributed Objects3. Software engineering:In software engineering, significant progress was made inthe development of Object-oriented design methods, leading tothe emergence of the Unified Modeling Language
DISTRIBUTED OBJECT TECHNOLOGIESDISTRIBUTED OBJECT TECHNOLOGIES• DCOM:DCOM is used for single platform, multiple languages.• JINI:• CORBA:CORBA is use for Multiple platforms, multiple languages
CORBA(COMMON OBJECT REQUEST BROKERARCITECTURER)
INTRODUCTIONDefinition:• CORBA is a distributed object-based systems.• Provides inter-operability• CORBA is a middle ware neither 2-tier or 3-tierarchitecture.• CORBA is a technology to communicate 2 objectswhich are of heterogeneous type.• CORBA can be written in c, c++, COBOL and JAVA
• CORBA was created by OMG(Object managementgroup).• OMG was created in 1989.• OMG does not provide any s/w products.• The first version of CORBA was released in July ,1992as• “OBJECT MANAGEMENT ARCITECTURE GUIDE”• Concept of CORBA came from OLE.
CORBA ArchitectureCORBA ArchitectureORB coreDynamicInvocationIDLStubsORBInterfaceObjectAdapterStatic IDLSkeletonDynamicSkeletonClient Object ImplementationInterfaceRepositoryImplementatioRepository
ORBORB• Object Request Broker.• Gives the communication infrastructure that iscapable of relaying object requests acrossdistributed platforms.• Client calls the Object implementation throughinterfaces provided by ORB.• Advantages:• Separates Client and Server implementation• Separates both client and Server from underlyingcommunication infrastructure and protocol stack and soreplaceable while migration from one implementation toother
• In Java we cannot separate a class’s definitionfrom its implementations as we can in C++• CORBA allows the separation of definition andimplementation• CORBA uses IDL for defining interfaces betweenclients and servers• ORB Vendors provide specific IDL compilers forsupported languages– create target language stubs and skeletons forbuilding CORBA clients and servers• C, C++, Smalltalk, Java, COBOL …Interface Definition LanguageInterface Definition Language
Client StubsClient Stubs• Client side proxy for server.• Joins to the client at one end and to the ORBcore at the other end.• Client-to-stub interface is decided by thestandard OMG language mapping for thechosen programming language.• Clients actually invoke methods on stubobjects.
Server SkeletonsServer Skeletons• Acts as client proxy for serverimplementation.• Connects– to the server object via the mapping defined forits programming language on .– To the Object Adapter via a proprietary interface.• Invocation pass through Object Adapter toskeletons, which in turn actually invokemethods on server object.
Object AdapterObject Adapter• Different kind of object implementations -– objects residing in their own process and requiringactivation.– others not requiring activation.• OA helps the ORB to operate with differenttype of objects.• Most widely used OA - BOA (Basic OA)• Recently standardized - POA (Portable OA)
Interface RepositoryInterface Repository• Contains information regarding the interfaces to ORBobjects.• Can be used by the ORB in 2 ways -– To provide type-checking of request signatures, whether a requestwas issued through DII or stub.– To check correctness of inheritance graph.• Client objects can use it -– To manage installation and distribution of interface definitionsaround your network.– Language compilers may use them to generate stubs and skeletons.• Can be shared by more than one ORB or one ORB may referto more than one interface repository.
Implementation RepositoryImplementation Repository• Contains all the information regardingobject implementation.• Provides a persistent record of how toactivate and invoke operations on objectimplementations.• CORBA gives vendors free-hand in handlingimplementations.
• Generic interface for making remoteinvocations.• Uses interface repository at run-time todiscover interfaces.• No need of pre-compiled stubs.Dynamic Invocation InterfaceDynamic Invocation Interface
Dynamic Skeleton InterfaceDynamic Skeleton Interface• Allows the ORB and OA to deliver requeststo an object without the need of pre-compiled skeletons.• Implemented via a DIR (Dynamic InvocationRoutine).• ORB invokes DIR for every DSI request itmakes.
Differences between DynamicDifferences between Dynamicinvocation and static invocationinvocation and static invocation• Use• SI used for general purpose• DI used for special purpose where extra flexibility is needed• In SI interfaces should be known at compile time , In DIinterfaces are discovered during run time using data ininterface repository• Static Interface are easier to use and code
CORBA servicesCORBA services• Clock service maintains synchronized time• Authentication service validates user id’s• Object storage service: a file system for objects• Life cycle service: oversees activation,deactivation, storage, check pointing, etc.• Transactions and replication services• Naming services• Security services
CORBA Advantages:• Interaction with legacy systems.• Static and dynamic method invocations• High-level language bindings• Location transparency• Built-in security and transactions
• Design and process deficiencies.• Problems with Firewalls.• Problems with implementation.CORBA PROBLEMSCORBA PROBLEMS
RMI Vs CORBARMI Vs CORBA• Language Barrier.• RMI can be easier to master than corba.corbais rich and extensive family of std andinterfaces.• Corba is peer-to-peer orb communicationmodel and Rmi is server centric model.• RMI interface is defined in RMI-IIOP and corbainterfaces are defined in IDL.
• Distributed object can be used like a regular object,but from anywhere on the network• Creation, migration and deletion of distributedobjects is different from local objects• CORBA RMI is multi-language RMI• Distributed objects may be executed in parallel.CONCLUSIONCONCLUSION
REFERENCESREFERENCES[1]www.omg.org[2]www.corba.org[3]en.wikipedia.org/wiki/Distributed_object[4]George Coulouris, Jean Dollimore, Tim Kindberg, Gordon Blair,“Distributed Systems Concepts and Design”, Pearson Press[5] http://www.cs.wustl.edu/~schmidt/corba-overview.html

Recommended

PPTX
Design Goals of Distributed System
PPT
Distributed Processing
PPTX
Unit 1
PPTX
Middleware Technologies ppt
PPT
clock synchronization in Distributed System
PDF
Middleware and Middleware in distributed application
PPTX
Message and Stream Oriented Communication
PPT
Lecture 1 (distributed systems)
PDF
CS9222 Advanced Operating System
PPTX
Transport layer
PPTX
Methods for handling deadlock
PPTX
Introduction to Distributed System
PPTX
Chapter 1 2 - some size factors
PPTX
Application Layer
PPTX
Statistical Software Quality Assurance.pptx
PPTX
Cohesion and coupling
PPTX
Message passing in Distributed Computing Systems
PPT
TCP/IP Network ppt
PPTX
Data Designs (Software Engg.)
PPTX
Deadlock ppt
ODP
Anatomy of android application
PPTX
Temporal databases
PDF
Mobile computing (Wireless) Medium Access Control (MAC)
PPT
Formal Specification in Software Engineering SE9
PPT
Distributed Transaction
PPT
Clock synchronization in distributed system
PPTX
Lecture 3 threads
PPT
Scheduling algorithms
PPTX
Corba concepts & corba architecture
PPT
Corba introduction and simple example

More Related Content

PPTX
Design Goals of Distributed System
PPT
Distributed Processing
PPTX
Unit 1
PPTX
Middleware Technologies ppt
PPT
clock synchronization in Distributed System
PDF
Middleware and Middleware in distributed application
PPTX
Message and Stream Oriented Communication
PPT
Lecture 1 (distributed systems)
Design Goals of Distributed System
Distributed Processing
Unit 1
Middleware Technologies ppt
clock synchronization in Distributed System
Middleware and Middleware in distributed application
Message and Stream Oriented Communication
Lecture 1 (distributed systems)

What's hot

PDF
CS9222 Advanced Operating System
PPTX
Transport layer
PPTX
Methods for handling deadlock
PPTX
Introduction to Distributed System
PPTX
Chapter 1 2 - some size factors
PPTX
Application Layer
PPTX
Statistical Software Quality Assurance.pptx
PPTX
Cohesion and coupling
PPTX
Message passing in Distributed Computing Systems
PPT
TCP/IP Network ppt
PPTX
Data Designs (Software Engg.)
PPTX
Deadlock ppt
ODP
Anatomy of android application
PPTX
Temporal databases
PDF
Mobile computing (Wireless) Medium Access Control (MAC)
PPT
Formal Specification in Software Engineering SE9
PPT
Distributed Transaction
PPT
Clock synchronization in distributed system
PPTX
Lecture 3 threads
PPT
Scheduling algorithms
CS9222 Advanced Operating System
Transport layer
Methods for handling deadlock
Introduction to Distributed System
Chapter 1 2 - some size factors
Application Layer
Statistical Software Quality Assurance.pptx
Cohesion and coupling
Message passing in Distributed Computing Systems
TCP/IP Network ppt
Data Designs (Software Engg.)
Deadlock ppt
Anatomy of android application
Temporal databases
Mobile computing (Wireless) Medium Access Control (MAC)
Formal Specification in Software Engineering SE9
Distributed Transaction
Clock synchronization in distributed system
Lecture 3 threads
Scheduling algorithms

Viewers also liked

PPTX
Corba concepts & corba architecture
PPT
Corba introduction and simple example
PPT
C O R B A Unit 4
PPTX
Corba
PPTX
Component object model and
ODP
Distributed operating system(os)
PDF
Component Object Model (COM, DCOM, COM+)
PPTX
Corba model ppt
PPT
Presentation On Com Dcom
PDF
Common Object Request Broker Architecture - CORBA
PPT
Data Warehousing and Data Mining
 
PPT
Dcom vs. corba
PPT
Ch12
PPT
Distributed Objects and JAVA
PPT
COM and DCOM
PPTX
Corba in power system
PDF
Distributed objects
PPT
Oopsla 2007 - The Web: Distributed Objects Realized!
PPT
Chapter7
Corba concepts & corba architecture
Corba introduction and simple example
C O R B A Unit 4
Corba
Component object model and
Distributed operating system(os)
Component Object Model (COM, DCOM, COM+)
Corba model ppt
Presentation On Com Dcom
Common Object Request Broker Architecture - CORBA
Data Warehousing and Data Mining
 
Dcom vs. corba
Ch12
Distributed Objects and JAVA
COM and DCOM
Corba in power system
Distributed objects
Oopsla 2007 - The Web: Distributed Objects Realized!
Chapter7

Similar to Distributed objects & components of corba

PPTX
PPT
Corba
PPTX
Common Object Request Broker Architecture
PPT
CORBA Basic and Deployment of CORBA
PDF
CORBA - Introduction and Details
DOCX
82159587 case-study-on-corba
PPTX
UNIT V DIS.pptx
PPT
ADVANCED JAVA MODULE III & IV.ppt
PPT
CORBA.ppt
PPTX
Corba
PPTX
corba-151024114450-lva1-app6891.pptx
PPT
Unit iv
PPTX
Distributing computing.pptx
DOCX
85305524 i-t-case-study
DOC
Introduction To Corba
PDF
corbaintroductionandexample-140703005744-phpapp02.pdf
PPT
MIDELWARE TECH
PPT
Chapter10
PPTX
ppt (1).pptx for corba common object resource broker
PPT
IntroJan14.ppt
Corba
Common Object Request Broker Architecture
CORBA Basic and Deployment of CORBA
CORBA - Introduction and Details
82159587 case-study-on-corba
UNIT V DIS.pptx
ADVANCED JAVA MODULE III & IV.ppt
CORBA.ppt
Corba
corba-151024114450-lva1-app6891.pptx
Unit iv
Distributing computing.pptx
85305524 i-t-case-study
Introduction To Corba
corbaintroductionandexample-140703005744-phpapp02.pdf
MIDELWARE TECH
Chapter10
ppt (1).pptx for corba common object resource broker
IntroJan14.ppt

Recently uploaded

PDF
[BDD 2025 - Full-Stack Development] The Modern Stack: Building Web & AI Appli...
PPTX
kernel PPT (Explanation of Windows Kernal).pptx
PDF
[BDD 2025 - Mobile Development] Exploring Apple’s On-Device FoundationModels
PDF
[BDD 2025 - Artificial Intelligence] Building AI Systems That Users (and Comp...
PDF
Lets Build a Serverless Function with Kiro
PDF
[BDD 2025 - Full-Stack Development] PHP in AI Age: The Laravel Way. (Rizqy Hi...
PPTX
The power of Slack and MuleSoft | Bangalore MuleSoft Meetup #60
PDF
[BDD 2025 - Mobile Development] Mobile Engineer and Software Engineer: Are we...
PDF
[BDD 2025 - Full-Stack Development] Digital Accessibility: Why Developers nee...
PDF
DUBAI IT MODERNIZATION WITH AZURE MANAGED SERVICES.pdf
PPTX
MuleSoft AI Series : Introduction to MCP
PPTX
"Feelings versus facts: why metrics are more important than intuition", Igor ...
 
PDF
ODSC AI West: Agent Optimization: Beyond Context engineering
PDF
So You Want to Work at Google | DevFest Seattle 2025
PPTX
Support, Monitoring, Continuous Improvement & Scaling Agentic Automation [3/3]
PDF
Cybersecurity Prevention and Detection: Unit 2
PDF
Integrating AI with Meaningful Human Collaboration
PDF
The Evolving Role of the CEO in the Age of AI
PDF
[BDD 2025 - Artificial Intelligence] AI for the Underdogs: Innovation for Sma...
PDF
"DISC as GPS for team leaders: how to lead a team from storming to performing...
 
[BDD 2025 - Full-Stack Development] The Modern Stack: Building Web & AI Appli...
kernel PPT (Explanation of Windows Kernal).pptx
[BDD 2025 - Mobile Development] Exploring Apple’s On-Device FoundationModels
[BDD 2025 - Artificial Intelligence] Building AI Systems That Users (and Comp...
Lets Build a Serverless Function with Kiro
[BDD 2025 - Full-Stack Development] PHP in AI Age: The Laravel Way. (Rizqy Hi...
The power of Slack and MuleSoft | Bangalore MuleSoft Meetup #60
[BDD 2025 - Mobile Development] Mobile Engineer and Software Engineer: Are we...
[BDD 2025 - Full-Stack Development] Digital Accessibility: Why Developers nee...
DUBAI IT MODERNIZATION WITH AZURE MANAGED SERVICES.pdf
MuleSoft AI Series : Introduction to MCP
"Feelings versus facts: why metrics are more important than intuition", Igor ...
 
ODSC AI West: Agent Optimization: Beyond Context engineering
So You Want to Work at Google | DevFest Seattle 2025
Support, Monitoring, Continuous Improvement & Scaling Agentic Automation [3/3]
Cybersecurity Prevention and Detection: Unit 2
Integrating AI with Meaningful Human Collaboration
The Evolving Role of the CEO in the Age of AI
[BDD 2025 - Artificial Intelligence] AI for the Underdogs: Innovation for Sma...
"DISC as GPS for team leaders: how to lead a team from storming to performing...
 
In this document
Powered by AI

Overview of distributed systems, and the concept of distributed objects and their interactions.

Explains remote object references and interfaces, highlighting invocation chains and exceptions.

Describes the progression of distributed objects from early middleware, programming languages, and software engineering.

Discussion of DCOM and CORBA as pivotal technologies for distributed object communication.

Detailed explanation of CORBA's architecture, including the object request broker and interface definitions.

Client stubs and server skeletons facilitate communication, backed by repository information for managing interfaces.

Dynamic Invocation and Skeleton Interfaces contrast with static invocation, focusing on runtime flexibility.

List of essential CORBA services and the advantages they provide, such as high-level language support and security.

Discusses problems with CORBA, including implementation issues and contrast with RMI, outlining their differences.

Final thoughts on distributed objects' functionalities, emphasizing their usage and operational differences.

List of resources and references for more detailed insights into CORBA and distributed object technology.

Distributed objects & components of corba

  • 1.
    Distributed Objects &ComponentsCORBAPresented By :Mayuresh Wadekar (52)Ajay Yadav (53)
  • 2.
    Distributed SystemDistributed System•Distributed System referred to computer networks where individualcomputers were physically distributed within some geographicalarea.Fig A. Difference Between Distributed & Parallel Computing
  • 3.
    Distributed ObjectDistributed Object•Distributed objects refers to software modules that are designed towork together, but reside either in multiple computers connectedvia a network or in different processes inside the same computerFig B. Distributed objects residing in different machines.
  • 4.
    Working of DistributedObjectsWorking of Distributed ObjectsFig C. Working of Distributed Objects
  • 5.
    Remote InvocationRemote InvocationFigD: Remote Invocation & Local Invocation
  • 6.
    DISTRIBUTED OBJECTSDISTRIBUTED OBJECTS•Remote object references:Globally unique reference for a distributed objects maybe passed as a parameter.• Distributed actions:Initiated by a method invocation, potentially resulting ininvocation chains.• Distributed exceptions:Additional exceptions generated from the distributednature of the system, including message loss or processfailure
  • 7.
    DISTRIBUTED OBJECTSDISTRIBUTED OBJECTS•Remote interfaces:Provides an abstract specification of the methods thatcan be invoked on the remote object.Fig D. Remote Interfaces
  • 8.
    EVOLUTION OF DISTRIBUTEDOBJECTSEVOLUTION OF DISTRIBUTED OBJECTS• Distributed objects as a natural evolution from threestrands of activity:1. Distributed systems:Earlier middleware was based on the client-server modeland there was a desire for more sophisticated programmingabstractions.2. Programming languages:Earlier work in object-oriented languages such as Simula-67and Smalltalk led to the emergence of more mainstream andheavily. Used programming languages such as Java and C++
  • 9.
    EVOLUTION OF DISTRIBUTEDOBJECTSEVOLUTION OF DISTRIBUTED OBJECTSFig E: OOP Distributed Objects3. Software engineering:In software engineering, significant progress was made inthe development of Object-oriented design methods, leading tothe emergence of the Unified Modeling Language
  • 10.
    DISTRIBUTED OBJECT TECHNOLOGIESDISTRIBUTEDOBJECT TECHNOLOGIES• DCOM:DCOM is used for single platform, multiple languages.• JINI:• CORBA:CORBA is use for Multiple platforms, multiple languages
  • 11.
    CORBA(COMMON OBJECT REQUESTBROKERARCITECTURER)
  • 12.
    INTRODUCTIONDefinition:• CORBA isa distributed object-based systems.• Provides inter-operability• CORBA is a middle ware neither 2-tier or 3-tierarchitecture.• CORBA is a technology to communicate 2 objectswhich are of heterogeneous type.• CORBA can be written in c, c++, COBOL and JAVA
  • 13.
    • CORBA wascreated by OMG(Object managementgroup).• OMG was created in 1989.• OMG does not provide any s/w products.• The first version of CORBA was released in July ,1992as• “OBJECT MANAGEMENT ARCITECTURE GUIDE”• Concept of CORBA came from OLE.
  • 14.
    CORBA ArchitectureCORBA ArchitectureORBcoreDynamicInvocationIDLStubsORBInterfaceObjectAdapterStatic IDLSkeletonDynamicSkeletonClient Object ImplementationInterfaceRepositoryImplementatioRepository
  • 15.
    ORBORB• Object RequestBroker.• Gives the communication infrastructure that iscapable of relaying object requests acrossdistributed platforms.• Client calls the Object implementation throughinterfaces provided by ORB.• Advantages:• Separates Client and Server implementation• Separates both client and Server from underlyingcommunication infrastructure and protocol stack and soreplaceable while migration from one implementation toother
  • 16.
    • In Javawe cannot separate a class’s definitionfrom its implementations as we can in C++• CORBA allows the separation of definition andimplementation• CORBA uses IDL for defining interfaces betweenclients and servers• ORB Vendors provide specific IDL compilers forsupported languages– create target language stubs and skeletons forbuilding CORBA clients and servers• C, C++, Smalltalk, Java, COBOL …Interface Definition LanguageInterface Definition Language
  • 17.
    Client StubsClient Stubs•Client side proxy for server.• Joins to the client at one end and to the ORBcore at the other end.• Client-to-stub interface is decided by thestandard OMG language mapping for thechosen programming language.• Clients actually invoke methods on stubobjects.
  • 18.
    Server SkeletonsServer Skeletons•Acts as client proxy for serverimplementation.• Connects– to the server object via the mapping defined forits programming language on .– To the Object Adapter via a proprietary interface.• Invocation pass through Object Adapter toskeletons, which in turn actually invokemethods on server object.
  • 19.
    Object AdapterObject Adapter•Different kind of object implementations -– objects residing in their own process and requiringactivation.– others not requiring activation.• OA helps the ORB to operate with differenttype of objects.• Most widely used OA - BOA (Basic OA)• Recently standardized - POA (Portable OA)
  • 20.
    Interface RepositoryInterface Repository•Contains information regarding the interfaces to ORBobjects.• Can be used by the ORB in 2 ways -– To provide type-checking of request signatures, whether a requestwas issued through DII or stub.– To check correctness of inheritance graph.• Client objects can use it -– To manage installation and distribution of interface definitionsaround your network.– Language compilers may use them to generate stubs and skeletons.• Can be shared by more than one ORB or one ORB may referto more than one interface repository.
  • 21.
    Implementation RepositoryImplementation Repository•Contains all the information regardingobject implementation.• Provides a persistent record of how toactivate and invoke operations on objectimplementations.• CORBA gives vendors free-hand in handlingimplementations.
  • 22.
    • Generic interfacefor making remoteinvocations.• Uses interface repository at run-time todiscover interfaces.• No need of pre-compiled stubs.Dynamic Invocation InterfaceDynamic Invocation Interface
  • 23.
    Dynamic Skeleton InterfaceDynamicSkeleton Interface• Allows the ORB and OA to deliver requeststo an object without the need of pre-compiled skeletons.• Implemented via a DIR (Dynamic InvocationRoutine).• ORB invokes DIR for every DSI request itmakes.
  • 24.
    Differences between DynamicDifferencesbetween Dynamicinvocation and static invocationinvocation and static invocation• Use• SI used for general purpose• DI used for special purpose where extra flexibility is needed• In SI interfaces should be known at compile time , In DIinterfaces are discovered during run time using data ininterface repository• Static Interface are easier to use and code
  • 25.
    CORBA servicesCORBA services•Clock service maintains synchronized time• Authentication service validates user id’s• Object storage service: a file system for objects• Life cycle service: oversees activation,deactivation, storage, check pointing, etc.• Transactions and replication services• Naming services• Security services
  • 26.
    CORBA Advantages:• Interactionwith legacy systems.• Static and dynamic method invocations• High-level language bindings• Location transparency• Built-in security and transactions
  • 27.
    • Design andprocess deficiencies.• Problems with Firewalls.• Problems with implementation.CORBA PROBLEMSCORBA PROBLEMS
  • 28.
    RMI Vs CORBARMIVs CORBA• Language Barrier.• RMI can be easier to master than corba.corbais rich and extensive family of std andinterfaces.• Corba is peer-to-peer orb communicationmodel and Rmi is server centric model.• RMI interface is defined in RMI-IIOP and corbainterfaces are defined in IDL.
  • 29.
    • Distributed objectcan be used like a regular object,but from anywhere on the network• Creation, migration and deletion of distributedobjects is different from local objects• CORBA RMI is multi-language RMI• Distributed objects may be executed in parallel.CONCLUSIONCONCLUSION
  • 30.
    REFERENCESREFERENCES[1]www.omg.org[2]www.corba.org[3]en.wikipedia.org/wiki/Distributed_object[4]George Coulouris, JeanDollimore, Tim Kindberg, Gordon Blair,“Distributed Systems Concepts and Design”, Pearson Press[5] http://www.cs.wustl.edu/~schmidt/corba-overview.html

[8]ページ先頭

©2009-2025 Movatter.jp