CORBA 2.6.1 Programmer's Guide for C++
Table Of Contents
- HP NonStop CORBA 2.6.1 Programmer's Guide for C++
- New and Changed Information
- Legal Notice
- 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. Using the IIOP/SSL API
- Chapter 12. Writing Wrappers for Legacy Clients and Servers
- Appendix A. Architectural Walkthrough
- Appendix B. Object References
- Appendix C. Servant Reference Counting in NonStop CORBA
- Index
The register_file_number() method in NSDEFw_GCF::Client, however, may be useful in server wrappers that issue nowait Pathsend requests
without the use of a jacket procedure. This method makes a file number returned by a Pathsend call available to the NonStop CORBA pthread
mechanism for I/O completions.
TCP/IP Socket Event Handlers and Event-Handler Users (Classes Fw_Event,
Fw_Sock_Client_EH, Fw_Sock_Server_EH, and Fw_Sock_Listener_EH)
The classes in the header file sockeh.h enable client, server, and listener event handlers to use the TCP/IP socket interfaces. These classes
provide:
An abstraction of a socket address (class Fw_Sock_Address)
A socket client event handler (class Fw_Sock_Client_EH) that implements Fw_Client_EH using the socket address abstraction
A socket listener event handler (class Fw_Sock_Listener_EH) that implements Fw_Listener_EH using the socket address abstraction
A socket server event handler (class Fw_Sock_Server_EH) that implements Fw_Server_EH using the socket address abstraction
A get/put recycling factory
Chapter 11. Using the IIOP/SSL API Appendix A. Architectural Walkthrough