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

Contains classes and methods for Guardian file-system I/O.
gcfehoss.h
Builds on the definitions in gfsehoss.h and adds classes and methods for TS/MP I/O.
sockeh.h
Contains classes and methods for TCP/IP socket I/O.
The $NSD_ROOT/include/nsdevent subdirectory also contains the vthread.h and timer.h header files,
whose contents are described in Writing Multithreaded Applications, and several other header files containing definitions
for NonStop CORBA internal use.
Caution
The classes described in the following sections contain some public methods that are required for internal use by
NonStop CORBA but are not recommended for application use. Applications should use only those methods that are
described in the NonStop CORBA 2.3 Programmer's Reference.
Base Event-Handler Interfaces
The event-handler interfaces are defined in the header file ehbase.h and consist of the following abstract classes:
Fw_Transfer_EH_User●
Fw_Transfer_EH●
Fw_Client_EH_User●
Fw_Client_EH●
Fw_Server_EH_User●
Fw_Server_EH●
Fw_Listener_EH_User●
Fw_Listener_EH●
The transfer classes, Fw_Transfer_EH_User and Fw_Transfer_EH, are base classes for the corresponding client
and server classes. Each of the other six classes represents a role that a client or server wrapper can play.
The event-handler interfaces operate on message objects and message data-descriptor objects, which are described in
Event Framework Messages and Message Data Descriptors.
For each method that your client or server wrapper uses from these abstract classes, your wrapper must either:
Implement the method, or●
Use the corresponding protocol-specific method from the event framework APIs for the Guardian file system
(defined in gfsehoss.h) or TCP/IP sockets (defined in sockeh.h).
●
Event Framework Messages and Message Data Descriptors
The Fw_MD and Fw_Message classes provide methods to assemble and disassemble messages for use by event handlers
and event-handler users. These classes are defined in the header file message.h.
Class Fw_MD