CORBA 2.3.3 Programmer's Guide for C++ (NonStop CORBA 2.3.3+)
Table Of Contents
- CORBA 2.3.3 Programmer's Guide for C++
- Legal Notice
- Contents
- About This Guide
- Chapter 1. Introduction to NonStop CORBA Programming
- Chapter 2. NonStop CORBA Administrative Environment
- Chapter 3. Compiling and Building an Application
- Chapter 4. Deploying a NonStop CORBA Application
- Chapter 5. Tracing and Debugging Applications
- Chapter 6. Writing Scalable Applications
- Chapter 7. Managing Transactions
- Chapter 8. Writing Multithreaded Applications
- Chapter 9. Designing Advanced Applications
- Chapter 10. Porting CORBA Applications to NonStop CORBA
- Chapter 11. Writing Wrappers for Legacy Clients and Servers
- Appendix A. Architectural Walkthrough
- Appendix B. Object References
- Appendix C. Servant Reference Counting in NonStop CORBA
- Index
A layered architecture view of the NonStop CORBA architecture would look like Figure A-3. In this view the application might be a client, a server,
or both. In all cases, the applications use IDL compiler-generated code to communicate with the ORB and POA. If the application needs the
Transaction Service, you can link in the OTS run-time.
The GIOP layer represents the general inter-ORB implementation. Below the GIOP there are three alternatives. An application might implicitly use
one or more of these alternatives depending upon the specific needs (the actual selection of the protocols is done through configuration):
Internet inter-ORB protocol (IIOP)●
GIOP over the Guardian file system●
GIOP over TS/MP●
The next layer represents the portability and event framework that supports the ORB and all of the protocols. Note that the vthreads API is included in
the event framework.
Figure A.3. Layered View of the NonStop CORBA Architecture
The following sections elaborate on the static view of NonStop CORBA components shown in Figures A-1 and A-2, by describing one way that
requests and responses flow between the components.