The omniORBpy version 3
User’s Guide

Duncan Grisby
(email: dgrisby@apasphere.com)
Apasphere Ltd.

July 2009

Changes and Additions, June 2007

- Updates for omniORBpy 3.1.

Changes and Additions, June 2005

- New omniORBpy 3 features.

Changes and Additions, July 2004

- Minor updates.

Changes and Additions, November 2002

- Per thread timeouts.
- Minor fixes.

Changes and Additions, August 2002

- Updated to omniORBpy 2.

Contents

- Introduction
  - Features
  - Setting up your environment
- The Basics
  - The Echo example
  - Generating the Python stubs
  - Object References and Servants
  - Example 1 — Colocated client and servant
  - Example 2 — Different Address Spaces
  - Example 3 — Using the Naming Service
  - Global IDL definitions
- Python language mapping issues
  - Narrowing object references
  - Support for Any values
  - Interface Repository stubs
- omniORB configuration and API
  - Setting parameters
  - Tracing options
  - Miscellaneous global options
  - Client side options
  - Server side options
  - GIOP and interoperability options
  - System Exception Handlers
  - Location forwarding
  - Dynamic importing of IDL
  - C++ API
- The IDL compiler
  - Common options
  - Python back-end options
  - Examples
- Interoperable Naming Service
  - Object URIs
  - Configuring resolve_initial_references
  - omniNames
  - omniMapper
  - Creating objects with simple object keys
- Connection and Thread Management
  - Background
  - The model
  - Client side behaviour
  - Server side behaviour
  - Idle connection shutdown
  - Transports and endpoints
  - Connection selection and acceptance
  - Bidirectional GIOP
  - SSL transport
- Code set conversion
  - Native code set
  - Code set library
  - Implementing new code sets
- Interceptors
- Objects by value
  - Features
  - Value sharing and local calls
  - Value factories
  - Standard value boxes
  - Values inside Anys
- References

> This document was translated from LATEX by H E V E A.